chore(sentry): decrease tracesSampleRate to prevent blowing through quota (#44901)

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

Chore

## What is the current behavior?

100% of traces are being sent to Sentry, which alone would blew through
all of our quota leaving no spans available for other projects. For
April we are already rate limited.

## What is the new behavior?

Change `tracesSampleRate` to more reasonable value (0.02).


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Optimized performance monitoring sampling configuration to reduce
application overhead while maintaining essential error tracking and
diagnostics.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

apps/studio/instrumentation-client.ts

@@ -97,7 +97,7 @@ Sentry.init({
   debug: false,
 
   // Enable performance monitoring
-  tracesSampleRate: 1.0, // Capture 100% of transactions for performance monitoring
+  tracesSampleRate: 0.02,
 
   integrations: (() => {
     const thirdPartyErrorFilterIntegration = (Sentry as any).thirdPartyErrorFilterIntegration

apps/studio/sentry.edge.config.ts

@@ -14,7 +14,7 @@ Sentry.init({
   debug: false,
 
   // Enable performance monitoring
-  tracesSampleRate: 1.0, // Capture 100% of transactions for performance monitoring
+  tracesSampleRate: 0.02,
   ignoreErrors: [
     'NEXT_NOT_FOUND',
     'NEXT_REDIRECT',

apps/studio/sentry.server.config.ts

@@ -13,7 +13,7 @@ Sentry.init({
   debug: false,
 
   // Enable performance monitoring
-  tracesSampleRate: 1.0, // Capture 100% of transactions for performance monitoring
+  tracesSampleRate: 0.02,
   ignoreErrors: [
     'ResizeObserver',
     'Failed to load Stripe.js',