chore(jeager-exporter): deprecate jaeger exporter

[pichlermarc]

Which problem is this PR solving?

The end of the Jaeger exporter support was announced in the spec (open-telemetry/opentelemetry-specification#2858). From July 2023 onwards, having a Jaeger Exporter will be optional. This PR adds a deprecation notice to the jsdoc of the exporter, as well as to the README.

• The Jeager client library used by this exporter is archived and will not receive any security updates
• Other SIGs are also planning to deprecate their exporters (or did already)
  • Java (see Deprecate jaeger exporters opentelemetry-java#5096)
  • Python (see Deprecate jaeger exporters opentelemetry-python#3121)
  • .NET (see Drop support for Jaeger Exporter opentelemetry-dotnet-instrumentation#1711)

The intention of this PR is to gather feedback if deprecating the exporter is something that we'd want to do. 🙂

Fixes #2618

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated

[codecov]

Codecov Report

Merging #3585 (67c09aa) into main (2f715bd) will decrease coverage by 0.02%.
The diff coverage is n/a.

❗ Current head 67c09aa differs from pull request most recent head 10a5fe6. Consider uploading reports for the commit 10a5fe6 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3585      +/-   ##
==========================================
- Coverage   93.64%   93.63%   -0.02%     
==========================================
  Files         275      275              
  Lines        8090     8076      -14     
  Branches     1679     1675       -4     
==========================================
- Hits         7576     7562      -14     
  Misses        514      514              

Impacted Files	Coverage Δ
...ckages/opentelemetry-exporter-jaeger/src/jaeger.ts	94.93% <ø> (ø)
...elemetry-instrumentation-grpc/src/grpc-js/index.ts	92.30% <0.00%> (-0.44%)	⬇️
...entelemetry-instrumentation-grpc/src/grpc/index.ts	93.98% <0.00%> (-0.31%)	⬇️

[Flarna]

I think we should deprecate it and also aim to remove it from the distribution/repo.

Do we have a defined deprecation cycle for GAed components?

Currently there is a pinned dependency to core and sdk-trace-base which is problematic in case we just stop releasing new versions. Maybe exclude it from lerna project and change these deps to ranges and then stop releasing it?

[blumamir]

I think the first step is to add the deprecation warning now.

In July 2023 it makes sense to have one last release with caret dependency and then deprecate it in npm. Do we need to keep it in the codebase after July 2023?

[naseemkullah]

created #3590 to track @Flarna's point of defining a deprecation strategy for GAed components, which we will apply to Jaeger exporter eventually

[pichlermarc]

I've now set the EOL date to March 2024 following the discussion in #3590, and have not set it to private: true.
It will be included in released until that date, then we can set private: true. WDYT @open-telemetry/javascript-approvers? 🙂

[dyladan]

I think the deprecation warning is enough