fix(ci): Remove global Spotlight env vars from E2E tests

Spotlight env vars (VITE_SENTRY_SPOTLIGHT, NEXT_PUBLIC_SENTRY_SPOTLIGHT)
should only be set for tests that specifically test Spotlight functionality.
Setting them globally was causing other tests to potentially behave
differently (e.g., adding Spotlight integration, making extra network
requests).

The nextjs-15-spotlight test already has NEXT_PUBLIC_SENTRY_SPOTLIGHT
set in its next.config.js, so it will continue to work.

Author: BYK

.github/workflows/build.yml

@@ -928,9 +928,8 @@ jobs:
       PUBLIC_E2E_TEST_DSN: 'https://username@domain/123'
       REACT_APP_E2E_TEST_DSN: 'https://username@domain/123'
       VITE_E2E_TEST_DSN: 'https://username@domain/123'
-      # For Spotlight environment variable tests
-      VITE_SENTRY_SPOTLIGHT: 'true'
-      NEXT_PUBLIC_SENTRY_SPOTLIGHT: 'true'
+      # Note: Spotlight env vars are NOT set globally - they should only be set
+      # in test apps that specifically test Spotlight functionality
       E2E_TEST_SENTRY_ORG_SLUG: 'sentry-javascript-sdks'
       E2E_TEST_SENTRY_PROJECT: 'sentry-javascript-e2e-tests'
     strategy:
@@ -1065,9 +1064,8 @@ jobs:
       PUBLIC_E2E_TEST_DSN: ${{ secrets.E2E_TEST_DSN }}
       REACT_APP_E2E_TEST_DSN: ${{ secrets.E2E_TEST_DSN }}
       VITE_E2E_TEST_DSN: ${{ secrets.E2E_TEST_DSN }}
-      # For Spotlight environment variable tests
-      VITE_SENTRY_SPOTLIGHT: 'true'
-      NEXT_PUBLIC_SENTRY_SPOTLIGHT: 'true'
+      # Note: Spotlight env vars are NOT set globally - they should only be set
+      # in test apps that specifically test Spotlight functionality
       E2E_TEST_SENTRY_ORG_SLUG: 'sentry-javascript-sdks'
       E2E_TEST_SENTRY_PROJECT: 'sentry-javascript-e2e-tests'
     strategy: