fix(e2e): revert Vite app to use production build with dev SDK exports

Reverted browser-webworker-vite to use 'vite build' + 'vite preview' because
the errors.test.ts tests expect production-style filenames (bundled .js files).

Added resolve.conditions to get SDK development exports during build,
enabling Spotlight auto-enablement while keeping production-like behavior
for worker tests.

Author: BYK

dev-packages/e2e-tests/test-applications/browser-webworker-vite/package.json

@@ -8,7 +8,7 @@
     "build": "rm -rf dist && tsc && vite build",
     "preview": "vite preview --port 3030",
     "test": "playwright test",
-    "test:build": "pnpm install",
+    "test:build": "pnpm install && pnpm build",
     "test:assert": "pnpm test"
   },
   "devDependencies": {

dev-packages/e2e-tests/test-applications/browser-webworker-vite/playwright.config.mjs

@@ -1,8 +1,7 @@
 import { getPlaywrightConfig } from '@sentry-internal/test-utils';
 
 const config = getPlaywrightConfig({
-  // Use vite dev server to test development-mode behavior (e.g., Spotlight auto-enablement)
-  startCommand: `pnpm dev`,
+  startCommand: `pnpm preview`,
   eventProxyFile: 'start-event-proxy.mjs',
   eventProxyPort: 3031,
   port: 3030,

dev-packages/e2e-tests/test-applications/browser-webworker-vite/vite.config.ts

@@ -13,6 +13,12 @@ export default defineConfig({
     },
   },
 
+  // Use development exports from @sentry/* packages to include Spotlight auto-enablement code
+  // The SDK has conditional exports: "development" includes Spotlight, "production" strips it
+  resolve: {
+    conditions: ['development', 'module', 'browser', 'import'],
+  },
+
   plugins: [
     sentryVitePlugin({
       org: process.env.E2E_TEST_SENTRY_ORG_SLUG,