feat: Add base config for JS loader with performance/replay

[mydea]

This PR adjusts the loader to include default config when enabling debug/performance/replay.

We should probably do a bit more testing etc. for this, as this is not really covered well as of now.
I did some tests locally with different scenarios, where stuff worked well, as far as I can tell.

Lazy mode

Lazy mode is only available for errors-only config. Users can manually opt-out of this by adding data-lazy="no" to their script tag.

In lazy mode, nothing happens until an error occurs. Once an error occurs, we download the CDN bundle, and then...:

• If onLoad is configured, trigger it
• If SDK.init() has not been called, call it with defaults

Eager mode

If either performance or replay is enabled, we are always in eager (non-lazy) mode. In this mode, we'll automatically load the CDN bundle, and then...:

• If onLoad is configured, trigger it
• If SDK.init() has not been called, call it with defaults

Defaults

The following default config is defined:

• dsn: Always set
• debug: true is set when debug bundles are enabled
• tracesSampleRate: 0.1 is set when performance is enabled
• replaysSessionSampleRate: 0.1 & replaysOnErrorSampleRate: 1 are set when replay is enabled
• integrations: Will add Sentry.BrowserTracing and/or Sentry.Replay if performance/replay is enabled

This config can be overwritten by the user, and is merged. So e.g. if they do:

Sentry.onLoad(function() {
  Sentry.init({
    tracesSampleRate: 0.5
  });
});

For a full loader build with every option enabled, the actual config will be:

{
  dsn: 'your-dsn',
  debug: true,
  tracesSampleRate: 0.5,
  replaysSessionSampleRate: 0.1,
  replaysOnErrorSampleRate: 1,
  integrations: [new Sentry.BrowserTracing(), new Sentry.Replay()]
}

Closes #46368

[mydea]

So I updated this quite a bit:

• Wrote tests in fix(loader): Ensure JS loader works with tracing & add tests sentry-javascript#7662 to actually test that the loader works with different combinations of lazy/products etc - this found some issues that we fixed in both repos 🎉
• Enforce that when performance or replay is enabled, we use SDK v7. This is also enforced UI-side now:

When you switch your SDK version to <7, it automatically removes performance & tracing. This should ensure we do not get into a weird state.

• When Replay is enabled, we show a message that this will result in the ES6 bundle:

ref #46436

[mydea]

Not so sure about the wording here... maybe:

When using Replay, Sentry is not ES5 compatible.

Or

When using Replay, we use the ES6 bundle of Sentry.

[AbhiPrasad]

We'll need to merge in the backend changes first - and then do the frontend.

This is still fine since everything is gated behind a feature flag.

[mydea]

We'll need to merge in the backend changes first - and then do the frontend.

This is still fine since everything is gated behind a feature flag.

Ah, oops - I extracted the UI stuff out into #46604

[mydea]

So I don't think the getsentry test failures are related to this PR...?

[HazAT]

Let's change the tracesSampleRate to 1. The reason, it's a weird experience if you expect a transaction to show up when testing, but it doesn't.

[getsentry-bot]

PR reverted: ed22b45