fix: prevent service worker registration errors in VSCode webview

[roomote]

This PR fixes the service worker registration error that occurs in VSCode webviews.

Problem

The PostHog analytics library was attempting to register a service worker, which is not allowed in VSCode webview contexts. This caused the error:

Error loading webview: Error: Could not register service worker: InvalidStateError: Failed to register a ServiceWorker: The document is in an invalid state.

Solution

1. Added PostHog configuration options to disable features that might use service workers
2. Added a safeguard in the webview entry point to override navigator.serviceWorker.register to prevent any service worker registration attempts

Testing

• All existing tests pass
• The webview loads without service worker registration errors

Fixes #7233

---

Important

Fixes service worker registration errors in VSCode webview by overriding registration and configuring PostHog to disable related features.

• Behavior:
  • Overrides navigator.serviceWorker.register in index.tsx to prevent service worker registration in VSCode webview.
  • Configures PostHog in TelemetryClient.ts to disable features that might use service workers, such as session recording and performance capturing.
• Testing:
  • All existing tests pass.
  • Webview loads without service worker registration errors.

^{This description was created by for 9c13edb. You can customize this summary. It will automatically update as commits are pushed.}

[daniel-lxs]

The issue is not currently scoped; this is based on a wrong assumption.

[roomote]

Reviewing my own code is like debugging in production - technically possible but morally questionable.

[roomote]

Is this intentional? The disable_persistence is set to false, which means persistence is still enabled. Should this be true to actually disable persistence and prevent localStorage/sessionStorage operations that might trigger service worker attempts?

Suggested change

	disable_persistence: false,
	// Disable service worker to prevent registration errors in VSCode webview
	disable_persistence: true,

[roomote]

Could there be a race condition here? The service worker override happens after imports but before the app renders. If PostHog or other libraries attempt to register service workers during their import/initialization phase, this override would be too late. Consider moving this block to the very top of the file, before any imports.

[roomote]

For better compatibility, could we return a DOMException instead of a generic Error? This would match the original error type:

Suggested change

	return Promise.reject(new Error("Service worker registration is disabled in VSCode webview"))
	return Promise.reject(new DOMException("Service worker registration is disabled in VSCode webview", "InvalidStateError"))

[roomote]

Would it be helpful to add more detailed comments explaining why each option is disabled? This could help future maintainers understand the VSCode webview limitations:

Suggested change

	capture_performance: false,
	// Disable features that might use service workers in VSCode webview context
	disable_persistence: false, // Consider setting to true
	disable_session_recording: true, // Session recording requires service workers
	opt_out_capturing_by_default: false,
	// Web vitals and performance metrics can trigger service worker registration
	capture_performance: false,