feat(bun, deno): Migrate request instrumentation to dataCollection

[chargome]

Migrates the Bun (bunServerIntegration) and Deno (wrapDenoRequestHandler) HTTP server instrumentation off the legacy sendDefaultPii flag and onto the dataCollection API

closes#20935

[chargome]

bugbot run

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

^{Reviewed by Cursor Bugbot for commit 63a127f. Configure here.}

[sentry]

Bug: Passing undefined from client?.getDataCollectionOptions() to httpHeadersToSpanAttributes causes a runtime crash when the Sentry client is not initialized.
_{Severity: CRITICAL}

Suggested Fix

Provide a fallback value to prevent passing undefined. Change the call to httpHeadersToSpanAttributes(request.headers.toJSON(), client?.getDataCollectionOptions() ?? false) to align with the pattern used in other integrations.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: packages/bun/src/integrations/bunserver.ts#L211-L213
Potential issue: When `getClient()` returns `undefined`, the expression
`client?.getDataCollectionOptions()` also evaluates to `undefined`. This `undefined`
value is then passed as the `dataCollection` argument to the
`httpHeadersToSpanAttributes` function. The function's default parameter is not
triggered when `undefined` is explicitly passed. Consequently, an internal variable
`resolvedDataCollection` becomes `undefined`, leading to a runtime error when the code
attempts to access `resolvedDataCollection.httpHeaders`. This can cause a server crash
during HTTP request handling if the Sentry client is not initialized.

Also affects:

• packages/bun/src/integrations/bunserver.ts:245~245

_{Did we get this right? 👍 / 👎 to inform future reviews.}