feat(node): Capture exceptions from worker_threads

[timfish]

Updates the childProcessIntegration to capture worker_threads errors (including their stack traces) rather than capturing a breadcrumb.

This features is enabled by default and can be disabled by setting the captureWorkerErrors option to false:

Sentry.init({
  dsn: 'https://public@dsn.ingest.sentry.io/1337',
  integrations: [Sentry.childProcessIntegration({ captureWorkerErrors: false })],
});

When captureWorkerErrors: false, a breadcrumb will be captured instead.

This PR also adds more integration tests for the childProcessIntegration.

[github-actions]

size-limit report 📦

Path	Size	% Change	Change
@sentry/browser	22.98 KB	-	-
@sentry/browser - with treeshaking flags	22.87 KB	-	-
@sentry/browser (incl. Tracing)	35.68 KB	-	-
@sentry/browser (incl. Tracing, Replay)	72.47 KB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.03 KB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	76.72 KB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	88.74 KB	-	-
@sentry/browser (incl. Feedback)	39.19 KB	-	-
@sentry/browser (incl. sendFeedback)	27.61 KB	-	-
@sentry/browser (incl. FeedbackAsync)	32.37 KB	-	-
@sentry/react	25.66 KB	-	-
@sentry/react (incl. Tracing)	38.46 KB	-	-
@sentry/vue	27.04 KB	-	-
@sentry/vue (incl. Tracing)	37.43 KB	-	-
@sentry/svelte	23.11 KB	-	-
CDN Bundle	24.36 KB	-	-
CDN Bundle (incl. Tracing)	36 KB	-	-
CDN Bundle (incl. Tracing, Replay)	70.64 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback)	75.79 KB	-	-
CDN Bundle - uncompressed	71.16 KB	-	-
CDN Bundle (incl. Tracing) - uncompressed	106.82 KB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	217.67 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	230.2 KB	-	-
@sentry/nextjs (client)	38.58 KB	-	-
@sentry/sveltekit (client)	36.21 KB	-	-
@sentry/node	156.21 KB	+0.03%	+36 B 🔺
@sentry/node - without tracing	97.36 KB	+0.04%	+35 B 🔺
@sentry/aws-serverless	106.77 KB	+0.04%	+40 B 🔺

View base workflow run

[AbhiPrasad]

Do the events captured from worker_threads get the correct trace id attached to them?

I wonder if we should be propagating the trace context to the worker threads scope with this integration as well 🤔

[timfish]

Currently this works even without Sentry running in the worker thread and because it uses captureException it will just use the main threads scope and trace context.

[AbhiPrasad]

Let's open a draft PR for this in the docs, we can only merge it in when we release v9 though.

I don't think we should backport this, we can make it a new feature for v9+