feat(cloudflare): propagate tracing context through Queue messages

[arthurfiorette]

Adds opt-in distributed tracing across Cloudflare Queue producers and consumers.

When enableQueueTracePropagation is enabled on both sides:

• Record-like message bodies carry sentry-trace and baggage under __sentry_queue_meta__.
• Arrays, binary payloads, and non-object payloads remain unchanged.
• Consumers remove the transport metadata before invoking the application handler.
• queue.process remains a root batch span and links to every producer represented in the batch.

Span links are used instead of continuing a producer trace because a Queue batch can contain messages from unrelated traces. Selecting one producer as the parent would create false causal relationships for the other messages.

The option is disabled by default because Cloudflare Queues does not expose a message-header API. Producers must modify record-like message bodies, so consumers without matching instrumentation may observe the additional metadata field.

Closes #22298

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

There are 4 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0bd582c. Configure here.}