fix(build): default to Node.js types, scope DOM types, @types/node -> 18.19.130

[overbalance]

Short description of changes

Removed dom and dom.iterable from root tsconfigs and explicitly added them only to packages that use DOM APIs.
Since tsconfigs are scoped to packages, any package that references DOM APIs needs dom types, even if the majority of that package's code targets Node.

Details

Inspired by the issue in #6278

• Remove dom and dom.iterable from the base tsconfig, defaulting all packages to Node.js types
• Update @types/node from 18.6.5 to 18.19.130 across all 41 packages (required for global performance type)
• Add DOM types explicitly to browser/isomorphic packages via tsconfig lib option
• Remove DOM types from API packages that don't need them
• Fix type errors exposed by stricter Node.js types

@types/node upgrade (18.6.5 → 18.19.130)

The global performance object type was added in @types/node 18.11.0. Without this upgrade, removing DOM types breaks packages that use performance directly.

Type fixes for @types/node 18.19.x

@opentelemetry/otlp-exporter-base

• Added override modifier to createConnection in test class extending http.Agent

@opentelemetry/instrumentation-http

• Fixed OutgoingHttpHeaders | readonly string[] type narrowing in utils.ts and test files
• In newer @types/node, request.headers can be a string array for raw headers

@opentelemetry/instrumentation-grpc

• Made patchedCallback function generic to fix type inference issues with SendUnaryDataCallback

@opentelemetry/sdk-trace-base

• Fixed TestExporterWithDelay callback to properly pass ExportResult through setTimeout

@opentelemetry/resources

• Fixed setTimeout resolve callback to pass undefined explicitly in tests

@opentelemetry/core

• Added explicit Performance type annotation to otperformance export in browser platform

API packages with DOM types removed

These packages don't use any DOM APIs, so DOM types are removed:

• @opentelemetry/api
• @opentelemetry/api-logs

Packages with DOM types added via tsconfig lib

These 17 packages need DOM types for browser APIs (fetch, XMLHttpRequest, navigator, VisibilityState, Performance, etc.):

Browser-only packages:

• @opentelemetry/sdk-trace-web
• @opentelemetry/context-zone-peer-dep
• @opentelemetry/web-common
• @opentelemetry/instrumentation-fetch
• @opentelemetry/instrumentation-xml-http-request
• @opentelemetry/opentelemetry-browser-detector

Isomorphic packages (browser + Node.js):

• @opentelemetry/core
• @opentelemetry/sdk-trace-base
• @opentelemetry/sdk-logs
• @opentelemetry/exporter-zipkin
• @opentelemetry/otlp-exporter-base
• @opentelemetry/exporter-trace-otlp-http
• @opentelemetry/exporter-trace-otlp-proto
• @opentelemetry/exporter-logs-otlp-http
• @opentelemetry/exporter-logs-otlp-proto
• @opentelemetry/exporter-metrics-otlp-http
• @opentelemetry/exporter-metrics-otlp-proto

Test plan

• npm run compile succeeds
• Full test suite passes

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.41%. Comparing base (0a9b614) to head (620f276).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6280   +/-   ##
=======================================
  Coverage   95.41%   95.41%           
=======================================
  Files         317      317           
  Lines        9597     9597           
  Branches     2220     2220           
=======================================
  Hits         9157     9157           
  Misses        440      440           

Files with missing lines	Coverage Δ
...ntelemetry-instrumentation-grpc/src/clientUtils.ts	96.73% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.