feat(replay): Do not capture errors originating from rrweb

[mydea]

rrweb can throw hard to pinpoint errors in its internals, e.g. when working with iframes or other hard to control environments.
We want to avoid flooding sentry errors with these, so this PR filters them out based on stracktrace.

Unless using captureExceptions experiment, we want to ignore these errors.

This is probably not 100% bullet proof, and relies on source maps etc. being correct, but I think it should help in a good amount of cases, at least.

Closes #6418

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.72 KB (0%)
@sentry/browser - ES5 CDN Bundle (minified)	61.13 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.51 KB (+0.02% 🔺)
@sentry/browser - ES6 CDN Bundle (minified)	54.66 KB (0%)
@sentry/browser - Webpack (gzipped + minified)	20.28 KB (0%)
@sentry/browser - Webpack (minified)	66.33 KB (0%)
@sentry/react - Webpack (gzipped + minified)	20.3 KB (0%)
@sentry/nextjs Client - Webpack (gzipped + minified)	47.5 KB (0%)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	26.69 KB (+0.02% 🔺)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	25.14 KB (0%)
@sentry/replay ES6 CDN Bundle (gzipped + minified)	41.83 KB (+0.33% 🔺)
@sentry/replay - Webpack (gzipped + minified)	38.08 KB (+0.32% 🔺)

[Lms24]

LGTM! As discuessed, let's see how this works out and if necessary make adjustments later. I think, having the captureExceptions flag to still enable sending these errors is good for debugging purposes 👍