fix(telemetry): close previous Sentry client before re-init to remove stale beforeExit listeners

LightNodeClient.startClientReportTracking() and enableLogs both register
process.on('beforeExit', ...) handlers that are only removed by calling
client.close(). Without closing the previous client before Sentry.init(),
re-calling initSentry (e.g. initSentry(false) in test afterEach) accumulates
stale listeners that fire async work (HTTP sends) on beforeExit, preventing
the bun process from exiting after tests complete.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: betegon

src/lib/telemetry.ts

@@ -355,6 +355,15 @@ export function initSentry(
   const libraryMode = options?.libraryMode ?? false;
   const environment = getEnv().NODE_ENV ?? "development";
 
+  // Close the previous client before re-initializing. LightNodeClient registers
+  // process.on('beforeExit', ...) listeners for client-report and log flushing
+  // via startClientReportTracking() and enableLogs. These are only removed by
+  // calling client.close(). Without this, re-initializing (e.g. initSentry(false)
+  // in test afterEach) accumulates stale listeners that keep the event loop alive
+  // after all tests complete, preventing the bun process from exiting.
+  // close(0) removes the listeners synchronously; we don't need to await the flush.
+  Sentry.getClient()?.close(0);
+
   const client = Sentry.init({
     dsn: SENTRY_CLI_DSN,
     enabled,