fix(profiling): reenable browser profiling (#46068)

Reenable browser profiling - once the base PR is merged, the base will
be changed and we can merge

---------

Co-authored-by: Ash Anand <ash.anand@sentry.io>
Co-authored-by: Ash Anand <0Calories@users.noreply.github.com>

static/app/bootstrap/initializeSdk.tsx

@@ -20,7 +20,7 @@ const SPA_MODE_ALLOW_URLS = [
 // We check for `window.__initialData.user` property and only enable profiling
 // for Sentry employees. This is to prevent a Violation error being visible in
 // the browser console for our users.
-const shouldEnableBrowserProfiling = false; // window?.__initialData?.user?.isSuperuser;
+const shouldEnableBrowserProfiling = window?.__initialData?.user?.isSuperuser;
 /**
  * We accept a routes argument here because importing `static/routes`
  * is expensive in regards to bundle size. Some entrypoints may opt to forgo