fix: glitchtip performance metrics + cleanup test submissions

- Refactor GlitchtipErrorReportingService to support dynamic DSN and tracesSampleRate
- Enable client-side performance tracing by setting tracesSampleRate: 0.1
- Configure production Mail variables and restart containers on alpha.mintel.me

lib/services/errors/glitchtip-error-reporting-service.ts

@@ -8,6 +8,8 @@ import type { LoggerService } from '../logging/logger-service';
 
 export type GlitchtipErrorReportingServiceOptions = {
   enabled: boolean;
+  dsn?: string;
+  tracesSampleRate?: number;
 };
 
 // GlitchTip speaks the Sentry protocol; @sentry/nextjs can send to GlitchTip via DSN.
@@ -46,12 +48,12 @@ export class GlitchtipErrorReportingService implements ErrorReportingService {
     if (!this.sentryPromise) {
       this.sentryPromise = import('@sentry/nextjs').then((Sentry) => {
         // Client-side initialization must happen here since sentry.client.config.ts is empty
-        if (typeof window !== 'undefined' && process.env.NODE_ENV === 'production') {
+        if (typeof window !== 'undefined' && this.options.enabled) {
           Sentry.init({
-            dsn: 'https://public@errors.infra.mintel.me/1',
+            dsn: this.options.dsn || 'https://public@errors.infra.mintel.me/1',
             tunnel: '/errors/api/relay',
             enabled: true,
-            tracesSampleRate: 0,
+            tracesSampleRate: this.options.tracesSampleRate ?? 0.1,
             replaysOnErrorSampleRate: 1.0,
             replaysSessionSampleRate: 0.1,
           });