fix(node): Guard against null httpVersion in outgoing request span attributes

On Node 22+ with Next.js 15, the bundled `@mswjs/interceptors` emits a
synthetic `response` event on request timeout/abort whose `IncomingMessage`
has `httpVersion === null`. `_getOutgoingRequestEndedSpanData` called
`httpVersion.toUpperCase()` unguarded, which crashed the process with an
unhandled rejection. The sibling server-side code in
`httpServerSpansIntegration` already optional-chains this attribute; this
brings the client path in line.

Fixes #20415

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: logaretm

packages/node-core/src/integrations/http/SentryHttpInstrumentation.ts

@@ -459,7 +459,10 @@ function _getOutgoingRequestSpanData(request: http.ClientRequest): [string, Span
 function _getOutgoingRequestEndedSpanData(response: http.IncomingMessage): SpanAttributes {
   const { statusCode, statusMessage, httpVersion, socket } = response;
 
-  const transport = httpVersion.toUpperCase() !== 'QUIC' ? 'ip_tcp' : 'ip_udp';
+  // httpVersion can be undefined in some cases and we seem to hav encountered this before:
+  // https://github.com/getsentry/sentry-javascript/blob/ec8c8c64cde6001123db0199a8ca017b8863eac8/packages/node-core/src/integrations/http/httpServerSpansIntegration.ts#L158
+  // see: #20415
+  const transport = httpVersion?.toUpperCase() !== 'QUIC' ? 'ip_tcp' : 'ip_udp';
 
   const additionalAttributes: SpanAttributes = {
     [ATTR_HTTP_RESPONSE_STATUS_CODE]: statusCode,