fix(replay): Ensure we normalize scope breadcrumbs to max. depth to avoid circular ref

[mydea]

After some in-depth debugging, I figured out that the replay may lock up if we do not normalize the scope breadcrumbs to a given depth.

This seems to fix the provided reproduction for me, and seems like a reasonable change overall.
10 is more or less a random value, but seems reasonable for me for this case?

it gets slower and slower with an increasing value there, becoming basically unusable around ~18-20.

I did some further digging, and the problem is that around a normalization of 20, it becomes crazy large:

console.log(JSON.stringify(normalize(breadcrumb, 20)));

results in a 60MB string 🤯

This is a simple first step to ensure we normalize all breadcrumbs to a max. depth. This applies to scope & dom breadcrumbs from Sentry itself.

This is not really a fix per se, as it could still be massive in shallow size. But it should help generally, and is perf-free (or even positive), as we are already walking this in normalize anyhow.

Ref https://github.com/getsentry/team-replay/issues/67

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	20.98 KB (-0.01% 🔽)
@sentry/browser - ES5 CDN Bundle (minified)	65.49 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	19.52 KB (-0.01% 🔽)
@sentry/browser - ES6 CDN Bundle (minified)	57.95 KB (0%)
@sentry/browser - Webpack (gzipped + minified)	21.12 KB (0%)
@sentry/browser - Webpack (minified)	68.9 KB (0%)
@sentry/react - Webpack (gzipped + minified)	21.14 KB (0%)
@sentry/nextjs Client - Webpack (gzipped + minified)	48.99 KB (0%)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	28.55 KB (0%)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	26.78 KB (+0.01% 🔺)
@sentry/replay ES6 CDN Bundle (gzipped + minified)	46.01 KB (+1.45% 🔺)
@sentry/replay - Webpack (gzipped + minified)	39.92 KB (+1.64% 🔺)
@sentry/browser + @sentry/tracing + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	64.87 KB (+1% 🔺)
@sentry/browser + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	57.85 KB (+1.14% 🔺)

[lforst]

We could use the normalizeDepth client option and set the max breadth to smth like 1_000 - which I find a sane number that will prevent an insane amount of data from being generated.

[mydea]

Hmm, I think we may want to have a dedicated setting for the depth here eventually, as we may not need as much depth here as in other places, for example. But a good point, will think about it. Will also add 1_000 as max properties, sounds like a good additional check!