test(node): Add tests for current DSC transaction name updating behavior

[Lms24]

This PR adds tests for DSC updating behaviour in the Node SDK, analogously to #13953

Currently, also in Node, we mutate the DSC and always include the most up to date transaction name

[Lms24]

I fought multiple hours with our test runner to get these tests working. Very frustrating.

Turns out, you can't assert on headers in the test server as well as on events in the same test. It will appear as if it's working but it won't fail if an assertion actually fails :/
moreover, there#s also super weird inter operation between expect and ecpectHeaders when you want to check on an event and its headers. After trying to make everything work in one test, I eventually gave up and made one for baggage and one for the trace envelope header.

I think part of the problem is that there is some race condition with the test server and the test runners both calling done which completely fucks up the assertion count.

[github-actions]

size-limit report 📦

Path	Size	% Change	Change
@sentry/browser	22.73 KB	-	-
@sentry/browser - with treeshaking flags	21.53 KB	-	-
@sentry/browser (incl. Tracing)	35.01 KB	-	-
@sentry/browser (incl. Tracing, Replay)	71.68 KB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	62.07 KB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	76.01 KB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	88.78 KB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	90.63 KB	-	-
@sentry/browser (incl. metrics)	27 KB	-	-
@sentry/browser (incl. Feedback)	39.87 KB	-	-
@sentry/browser (incl. sendFeedback)	27.38 KB	-	-
@sentry/browser (incl. FeedbackAsync)	32.17 KB	-	-
@sentry/react	25.49 KB	-	-
@sentry/react (incl. Tracing)	37.97 KB	-	-
@sentry/vue	26.91 KB	-	-
@sentry/vue (incl. Tracing)	36.9 KB	-	-
@sentry/svelte	22.87 KB	-	-
CDN Bundle	24.11 KB	-	-
CDN Bundle (incl. Tracing)	36.84 KB	-	-
CDN Bundle (incl. Tracing, Replay)	71.47 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback)	76.78 KB	-	-
CDN Bundle - uncompressed	70.7 KB	-	-
CDN Bundle (incl. Tracing) - uncompressed	109.36 KB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	221.72 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	234.94 KB	-	-
@sentry/nextjs (client)	37.94 KB	-	-
@sentry/sveltekit (client)	35.6 KB	-	-
@sentry/node	124.9 KB	-0.01%	-1 B 🔽
@sentry/node - without tracing	94.13 KB	-	-
@sentry/aws-serverless	103.7 KB	-0.01%	-1 B 🔽

View base workflow run

[codecov]

❌ 6 Tests Failed:

Tests completed	Failed	Passed	Skipped
638	6	632	26

View the top 3 failed tests by shortest run time

tracing/trace-lifetime/pageload-meta/test.ts create a new trace for a navigation after the <meta> tag pageload trace

Stack Traces | 0.233s run time

test.ts:18:11 create a new trace for a navigation after the <meta> tag pageload trace

tracing/trace-lifetime/pageload-meta/test.ts error during <meta> tag pageload has pageload traceId

Stack Traces | 0.312s run time

test.ts:136:11 error during <meta> tag pageload has pageload traceId

tracing/trace-lifetime/pageload-meta/test.ts outgoing XHR request during <meta> tag pageload has pageload traceId in headers

Stack Traces | 0.338s run time

test.ts:247:11 outgoing XHR request during <meta> tag pageload has pageload traceId in headers

To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard

[s1gr1d]

Looks good, I think it's okay to just add tests for the stuff that didn't fall into a race condition. But what a bummer that this didn't work :/