feat(sdk-trace-web): deprecate instrumentation utilities

[keshav-019]

Which problem is this PR solving?

@opentelemetry/sdk-trace-web currently exports instrumentation-specific utilities and supporting types. These utilities should be owned by the instrumentation packages that consume them so they can eventually be removed from the SDK.

Fixes #5869

Short description of the changes

• Mark all 15 instrumentation utility exports listed in [sdk-trace-web] deprecate instrumentation utilities in SDK package #5869 as deprecated.
• Direct instrumentation packages to copy the required implementations or definitions locally.
• Document that the exports will be removed in a future major release.
• Add an Unreleased changelog entry.
• Preserve existing runtime behavior.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• npm.cmd run lint --workspace=@opentelemetry/sdk-trace-web
• npm.cmd run compile --workspace=@opentelemetry/sdk-trace-web
• npm.cmd run compile --ignore-scripts
• Browser suite: 60/60 tests passed using Headless Chrome with GPU disabled for the local sandbox
• Web Worker suite: 50/50 tests passed using Headless Chrome with GPU disabled for the local sandbox
• Generated declaration audit confirmed all 15 exports retain @deprecated metadata

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added (not applicable: documentation-only deprecations with no runtime changes)
• Documentation has been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: keshav-019 / name: Keshav (0d9d482)

[github-actions]

Welcome, contributor! Thank you for your contribution to opentelemetry-js.

Important reminders:

• Read our Contributing Guidelines.

• Sign the CLA if you haven't already.

• Follow the OpenTelemetry Generative AI policy: disclose any AI use in your contribution, and communicate (PR descriptions, review replies) in your own words rather than AI-generated text.

• Give reviewers at least a few days before pinging them for feedback.

• If you need help with general setup, development process, or contributor etiquette, ask in #opentelemetry-new-contributors.

• Add an entry describing your change to the appropriate changelog file: Stable packages, Experimental packages, API or Semantic Conventions. Add your entry under the ## Unreleased section.

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on reviewers · refreshed 2026-09-02 16:39 UTC

Review the latest changes.

Also blocked by: Merge conflicts.

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.