feat(nextjs): Add request data to all edge-capable functionalities

[lforst]

This PR adds RequestData capabilities to the Vercel Edge SDK. We do not include the capabilities by default until the next major because suddenly including it may leak PII.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	66.02 KB (0%)
@sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped)	56.21 KB (0%)
@sentry/browser (incl. Tracing) - Webpack (gzipped)	31.19 KB (0%)
@sentry/browser - Webpack (gzipped)	21.4 KB (0%)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	62.65 KB (0%)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	29.47 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped)	21.55 KB (0%)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	197.27 KB (0%)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	89.15 KB (0%)
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	64.12 KB (0%)
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	32.12 KB (0%)
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	66.43 KB (0%)
@sentry/react - Webpack (gzipped)	21.45 KB (0%)
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	83.16 KB (0%)
@sentry/nextjs Client - Webpack (gzipped)	48.32 KB (0%)
@sentry-internal/feedback - Webpack (gzipped)	16.19 KB (0%)

[lforst]

@AbhiPrasad it seems like we can't use the TS built-in Request, Response etc. types because it requires the DOM TS types extension so I started vendoring them: 5672479

[whitep4nth3r]

Is this specifically for Vercel? Just wondering how this would play nicely with other platforms such as Netlify.

[lforst]

Is this specifically for Vercel? Just wondering how this would play nicely with other platforms such as Netlify.

@whitep4nth3r This will currently pretty much only apply to the Next.js SDK but for all hosting platforms. We just named the vercel-edge SDK horribly. (shaking fist angrily) wintercg would have probably been a better name.

[AbhiPrasad]

We just named the vercel-edge SDK horribly

Actually no we didn't because vercel edge has async local storage support, while this is not part of the wintercg spec. So something like cloudflare would not work with the vercel-edge sdk.

I think core is our wintercg compatible sdk,

[lforst]

We just named the vercel-edge SDK horribly

Actually no we didn't because vercel edge has async local storage support, while this is not part of the wintercg spec. So something like cloudflare would not work with the vercel-edge sdk.

I think core is our wintercg compatible sdk,

Right. I keep forgetting this. Sorry!