feat(node): Add tracePropagationTargets option

[lforst]

This PR adds the tracePropagationTargets option as outlined in #5403, getsentry/develop#636, and DACI (internal) to the node SDK init options.

The tracePropagationTargets option can be used to control to which request the SDK should attach trace data (at the time of writing via sentry-trace and baggage headers).

Its behavior (at least for node) is as follows: If not provided, the SDK will attach tracing data to all outgoing requests. If provided, the SDK will only attach trace data when the request's URL matches one of the items in the tracePropagationTargets array.

Resolves #5403

---

Notes:

• Since the option has a different meaning in the node SDK vs the browser SDK, I suggest we have the option types separated so we can have different JSDoc for each of them.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.36 KB (0%)
@sentry/browser - ES5 CDN Bundle (minified)	59.96 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	17.94 KB (-0.02% 🔽)
@sentry/browser - ES6 CDN Bundle (minified)	52.83 KB (0%)
@sentry/browser - Webpack (gzipped + minified)	19.7 KB (0%)
@sentry/browser - Webpack (minified)	64.17 KB (0%)
@sentry/react - Webpack (gzipped + minified)	19.72 KB (0%)
@sentry/nextjs Client - Webpack (gzipped + minified)	44.14 KB (0%)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	25.77 KB (-0.01% 🔽)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	24.02 KB (-0.01% 🔽)

[Lms24]

This looks great. And I agree, having a browser/node-specific JSDoc justifies defining the option twice.

Just had some minor questions and remarks but nothing blocking.

Also, thanks for taking the time and adding all these tests despite this change being tough to test properly!

[Lms24]

optional/question: Does it make sense to extract (string | RegExp)[] | undefined to a type?

[lforst]

Yeah that makes a lot of sense! Can you check whether the location where I extracted it makes sense?: 0aa153f

Also I extracted it without | undefined because that works better with the optional operator in the init options.

[Lms24]

I think it sort of makes sense but I can see why this might look a little off. Seems like we don't really have a tracing-related file in the types package. Adding it to the transaction, span or baggage files also doesn't make more sense...

So wdyt about adding a new tracing.ts file? Or we add it to the misc.ts file ?

[lforst]

Created a tracing.ts file. Thanks for the input!