feat(deno): Add incoming request options to denoServeIntegration

[isaacs]

Deno.serve is the server most Deno apps use, but its integration only took maxRequestBodySize and the deprecated ignoreStatusCodes. A user could not skip body capture for one route, such as a health check, an upload, or a route that receives secrets. denoHttpIntegration, Node and Cloudflare all allow this.

denoServeIntegration now accepts ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated and onSpanEnd. They use the same names and behavior as denoHttpIntegration, but the callbacks receive the web Request.

The options follow core's node:http server code. urlPath includes the query string, and the static asset filter applies only to GET. When the SDK skips a span, it still continues the incoming trace, attaches request data and the body, and captures errors. For a streamed response, onSpanEnd runs when the stream finishes. It does not run when the handler throws, because there is no Response to pass.

Two defaults change behavior. ignoreStaticAssets defaults to true, so GET requests for files such as favicon.ico or *.js no longer create spans. spans defaults to the client's tracing configuration, so the integration no longer starts spans when tracing is disabled.

Request sessions for Deno.serve and the same options for Bun.serve remain separate work.

Fixes #25492
Fixes JS-3955

[linear-code]

JS-3955

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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