Support `propagateTraceParent` in Server-side SDKs

[Lms24]

Problem Statement

In #17509, we added support to optionally send the W3C traceparent header in outgoing requrests, alongside our sentry-trace and baggage headers to our browser SDKs.

Today, this option is not exposed or supported in our server SDKs. Users are requesting an option to send traceparent headers from a sentry-instrumented backend to an OTel/OTLP instrumented backend.

Solution Brainstorm

We should add support for this option in our server SDKS:

• Deno (via Node SDK?)
• Bun (we probably get for free via Node SDK)
• Vercel Edge (I'd say low prio but if it's easily doable why not)
• Update docs around propagateTraceparent. We can just remove the guard that shows it in only in browser guides right now.

Out of Scope

Accepting, reading or continuing traces from incoming traceparent headers.

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1184

[timfish]

I think once #18569 has been merged we can close this. Everywhere we already inject sentry-trace headers should now support traceparent.