build: upgrade TypeScript to 5.9.2, fix CommonJS module resolution

[overbalance]

DRAFT

What this does

Upgrades TypeScript from 5.0.4 to 5.9.2 and hoists all build devDependencies to the root package.json.

• Disk space saved: 58MB (7.4% reduction)
• Package count: 349 fewer packages (12.2% reduction)

Key changes

TypeScript configuration

• Changed module resolution from node16 to node/bundler (TS 5.9.2 requires file extensions with node16)
• Added skipLibCheck: true to instrumentation-openai for @types/node compatibility issues

Test fixes

• Updated karma configs to load plugins from root after dependency hoisting
• Fixed webpack process polyfill path for ESM compatibility
• Updated expect import syntax for socket.io tests
• Fixed AWS SDK mock response Content-Length headers

Dependencies

• All build devDependencies moved to root package.json
• Added missing dependencies (formdata-node, etc.)
• Removed unused jQuery dependencies

Package-specific changes

@opentelemetry/instrumentation-socket.io

• Changed import * as expect to import expect (expect v29 uses default export)

@opentelemetry/instrumentation-dns

• Added type annotations for mock resolver callbacks

@opentelemetry/instrumentation-aws-sdk

• Fixed Bedrock mock response Content-Length headers
• Added path mapping for semantic-conventions/incubating imports

@opentelemetry/instrumentation-openai

• Added skipLibCheck: true for @types/node Buffer/ArrayBuffer incompatibilities
• Added formdata-node dependency

@opentelemetry/resource-detector-gcp

• Added .mocharc.json for ESM/TypeScript loader
• Added missing json-bigint and google-logging-utils dependencies

Browser packages (propagator-aws-xray, propagator-instana, instrumentation-user-interaction, instrumentation-long-task)

• Updated karma.conf.js to load plugins from root package.json

The changes are mostly mechanical fixes required by the TypeScript upgrade and dependency restructuring.

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.

[pichlermarc]

FYI upgrading typescript is often a breaking change as the typescript project does not follow Semantic Versioning for the output it produces.

[overbalance]

FYI upgrading typescript is often a breaking change as the typescript project does not follow Semantic Versioning for the output it produces.

For sure. I've been playing with the version number to see how far we can comfortably upgrade. It's whack-a-mole with this much code so I'm thinking we leave it at 5.0.4, and focus on consolidating the devdependencies.