ref(nextjs): Remove all deprecated API

[lforst]

Removes all deprecated code from the Next.js package.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped)	78.16 KB (-0.22% 🔽)
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	69.37 KB (-0.29% 🔽)
@sentry/browser (incl. Tracing, Replay with Canvas) - Webpack (gzipped)	73.31 KB (-0.25% 🔽)
@sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped)	63.01 KB (-0.26% 🔽)
@sentry/browser (incl. Tracing) - Webpack (gzipped)	33.35 KB (-0.5% 🔽)
@sentry/browser (incl. browserTracingIntegration) - Webpack (gzipped)	33.22 KB (-0.51% 🔽)
@sentry/browser (incl. Feedback) - Webpack (gzipped)	31.2 KB (-0.54% 🔽)
@sentry/browser (incl. sendFeedback) - Webpack (gzipped)	31.21 KB (-0.53% 🔽)
@sentry/browser - Webpack (gzipped)	22.48 KB (-0.69% 🔽)
@sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped)	76.19 KB (-0.23% 🔽)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	67.71 KB (-0.28% 🔽)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	33.47 KB (-0.56% 🔽)
@sentry/browser - ES6 CDN Bundle (gzipped)	24.56 KB (-0.7% 🔽)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	213.68 KB (-0.19% 🔽)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	101.48 KB (-0.39% 🔽)
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	73.86 KB (-0.54% 🔽)
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	36.64 KB (-0.44% 🔽)
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	69.76 KB (-0.24% 🔽)
@sentry/react - Webpack (gzipped)	22.52 KB (-0.66% 🔽)
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	87.53 KB (-0.02% 🔽)
@sentry/nextjs Client - Webpack (gzipped)	50.42 KB (-2.52% 🔽)
@sentry-internal/feedback - Webpack (gzipped)	17.2 KB (-0.1% 🔽)

[mydea]

l: We can refactor this later, but IMHO we can simplify this by just passing the client in here and directly calling the start span methods from core here?

[lforst]

I don't follow ^^ Do you mind elaborating? Or do you have examples where we do something similar?

[mydea]

is this not the same as leaving the ?? undefined away here? (or is it bad if this returns null, not sure if this is possible) - just because we don't do it below :)

[lforst]

It's a bit ridiculous but continueTrace doesn't take null as sentryTrace value so we need to turn it into undefined. I wanted to change that anyhow. I'll clean this up in a follow-up.

[lforst]

@mydea I am blocked to migrate traceparentData and tags to the scope because the current browserTracingIntegration implementation doesn't pick them up yet. I would do that in a follow-up.