feat(nestjs): Deprecate @WithSentry in favor of @SentryExceptionCaptured

[lforst]

Ref #14293

[github-actions]

size-limit report 📦

Path	Size	% Change	Change
@sentry/browser	22.8 KB	-	-
@sentry/browser - with treeshaking flags	21.57 KB	-	-
@sentry/browser (incl. Tracing)	35.31 KB	-	-
@sentry/browser (incl. Tracing, Replay)	72.06 KB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	62.43 KB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	76.35 KB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	88.79 KB	-	-
@sentry/browser (incl. Feedback)	39.56 KB	+0.01%	+1 B 🔺
@sentry/browser (incl. sendFeedback)	27.45 KB	-	-
@sentry/browser (incl. FeedbackAsync)	32.27 KB	-	-
@sentry/react	25.58 KB	-	-
@sentry/react (incl. Tracing)	38.26 KB	-	-
@sentry/vue	26.95 KB	-	-
@sentry/vue (incl. Tracing)	37.14 KB	-	-
@sentry/svelte	22.94 KB	-	-
CDN Bundle	24.16 KB	+0.02%	+3 B 🔺
CDN Bundle (incl. Tracing)	37.11 KB	-	-
CDN Bundle (incl. Tracing, Replay)	71.78 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback)	77.12 KB	-	-
CDN Bundle - uncompressed	70.86 KB	-	-
CDN Bundle (incl. Tracing) - uncompressed	110.07 KB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	222.59 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	235.81 KB	-	-
@sentry/nextjs (client)	38.37 KB	-	-
@sentry/sveltekit (client)	35.88 KB	-	-
@sentry/node	134.4 KB	-0.01%	-1 B 🔽
@sentry/node - without tracing	96.25 KB	-	-
@sentry/aws-serverless	106.54 KB	-	-

View base workflow run

[chargome]

What is the reason for creating the deprecation pr separately?

[lforst]

What is the reason for creating the deprecation pr separately?

It gives us the possibilty to publish a version that has the migration path layed out, so that we can update the docs in peace to point to the newer version.

That way we never have docs that tell people to use a deprecated thing. This is one of the learnings we had in v8. For things that we expect to have close to 0 direct usage we can skip this circus but I assume this has a lot of usage.