build: Update size limit config

[mydea]

This updates the size limit config a bit, to be a bit more structured.

• Drop all non-gzipped entries. IMHO it is good enough to have the gzipped values, and it makes it a bit clearer and easier to compare. Not sure if we want to add e.g. a single non-gzipped one, but honestly I don't know when we would really care about that?
• Reorder entries (not 100% sure TBH if the order is actually considered in the UI, though 😅 ).
• Added webpack scenarios exporting just { init }, or { init, BrowserTracing } or { init, BrowserTracing, Replay } to have a realistic coverage of these scenarios.
• Removed some secondary scenarios (e.g. there is just a single ES5 CDN bundle scenario left to cover this, not for all variations, ...

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	0 B (removed)
@sentry/browser - ES5 CDN Bundle (minified)	0 B (removed)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	0 B (removed)
@sentry/browser - ES6 CDN Bundle (minified)	0 B (removed)
@sentry/browser - Webpack (gzipped + minified)	0 B (removed)
@sentry/browser - Webpack (minified)	0 B (removed)
@sentry/react - Webpack (gzipped + minified)	0 B (removed)
@sentry/nextjs Client - Webpack (gzipped + minified)	0 B (removed)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	0 B (removed)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	0 B (removed)
@sentry/replay ES6 CDN Bundle (gzipped + minified)	0 B (removed)
@sentry/replay - Webpack (gzipped + minified)	0 B (removed)
@sentry/browser + @sentry/tracing + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	0 B (removed)
@sentry/browser + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	0 B (removed)
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	75 KB (added)
@sentry/browser (incl. Tracing) - Webpack (gzipped)	31.35 KB (added)
@sentry/browser - Webpack (gzipped)	21.95 KB (added)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	69.76 KB (added)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.24 KB (added)
@sentry/browser - ES6 CDN Bundle (gzipped)	20.33 KB (added)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	220.79 KB (added)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	85.9 KB (added)
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	60.48 KB (added)
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	30.37 KB (added)
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	65.13 KB (added)
@sentry/react - Webpack (gzipped)	21.96 KB (added)
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	92.85 KB (added)
@sentry/nextjs Client - Webpack (gzipped)	50.83 KB (added)

[AbhiPrasad]

I would keep the minified value - it's a better analog to parse time and easier to track changes over time. https://blog.sentry.io/javascript-sdk-package-reduced/

We chose to track the minified CDN bundle over the gzipped + minified CDN bundle because the minified bundle is more representative of the bundle executed at runtime. The bundle size at runtime has a direct relationship with parse and execution time, so minimizing the minified bundle would minimize the time Sentry blocked the main thread. It’s much easier to track the impact individual changes had against the minified bundle size versus the total gzipped + minified bundle size.

We can just keep it for the CDN bundles though.