fix: prevent Sentry module loading entirely during test execution

- Move Sentry import to conditional dynamic import in main entry point
- Prevents module loading conflicts that cause 'module is already linked' errors
- Uses comprehensive test environment detection for all CI systems
- Ensures tests run without any Sentry initialization or module conflicts

Author: cameroncooke

src/index.ts

@@ -13,8 +13,22 @@
  * - Handling server lifecycle events
  */
 
-// Import Sentry instrumentation
-import './utils/sentry.js';
+// Import Sentry instrumentation only if not in test environment
+const isTestEnvironment =
+  process.env.NODE_ENV === 'test' ||
+  process.env.VITEST === 'true' ||
+  process.env.CI === 'true' ||
+  process.env.GITHUB_ACTIONS === 'true' ||
+  process.argv.some((arg) => arg.includes('vitest')) ||
+  (typeof global !== 'undefined' && 'vitest' in global) ||
+  (typeof process !== 'undefined' && process.env.npm_lifecycle_event === 'test');
+
+// Initialize Sentry asynchronously only in production environments
+if (!isTestEnvironment) {
+  (async (): Promise<void> => {
+    await import('./utils/sentry.js');
+  })();
+}
 
 // Import server components
 import { createServer, startServer } from './server/server.js';