feat(bun): Add client address, port and protocol to Bun.serve spans

[Shubham-Padkonde]

Closes #23886

Bun.serve spans now set client.address, client.port and network.protocol.name, matching Deno.serve (wrap-deno-request-handler.ts).

• Bun passes the Server as the second argument to both fetch and route handlers. wrapRequestHandler reads it from args[1] and calls server.requestIP(request), so the server doesn't have to be threaded through the proxies.
• As in Deno, the first x-forwarded-for entry wins over the socket address for client.address, and both attributes are gated on dataCollection.userInfo.
• network.protocol.name is always http.
• requestIP is guarded by a type check and a try/catch, so a missing or throwing implementation (for example on a request that didn't come from the server's socket) just leaves the attributes unset.

Tests

There are 4 new tests in packages/bun/test/integrations/bunserver.test.ts, covering:

• defaults on a fetch handler;
• route handlers;
• x-forwarded-for precedence;
• userInfo: false.

Results, run locally with Bun 1.4.2:

• bun test test/integrations/bunserver.test.ts: 31 pass. With the develop version of bunserver.ts, the 4 new tests fail.

• bun test in packages/bun: 66 pass, 0 fail.

• oxlint --type-aware and oxfmt --check are clean on both files, and tsc -p tsconfig.types.json --noEmit is clean.

• If you've added code that should be tested, please add tests.

• Ensure your code lints and the test suite passes.

• Link an issue if there is one related to your pull request.

This change was written with help from an AI coding assistant (Claude Code). I reviewed and tested it as described above.

🤖 Generated with Claude Code