fix(sdk-node): lazy require @opentelemetry/exporter-jaeger

[pichlermarc]

Which problem is this PR solving?

The JaegerExporter currently does not support running in bundled environments, as requiring jaeger-client loads .thrift files from the file system. This causes problems in @opentelemetry/sdk-node as the JaegerExporter is required even though it is unused, see #3521).

To circumvent this problem, this PR changes the approach of always requiring '@opentelemetry/exporter-jaeger' to do it once before the constructor is actually called. Further added documentation to clarify that bundling is not supported with this package.

This PR does not add support for running the JaegerExporter in a bundled environment.

Fixes #3521
Supersedes #3728

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• Manual testing using the repoducer from Can't update to @opentelemetry/sdk-node v0.34.0 using esbuild #3521
• Existing unit tests

Alternatives I have considered

• Pulling in relevant code from jaeger-client and pre-generating JS code from the .thrift files.
  • I decided against doing this as it would increase the maintenance burden on this repo, and would require significantly more work to get right.
• Removing the JaegerExporter from sdk-node
  • The sdk-node @opentelemetry/exporter-jaeger package is deprecated, but I decided against doing this as it would break existing JaegerExporter users of the sdk-node package without warning.
• Lazy requiring the jaeger-client library (see fix(exporter-jaeger): lazy require jaeger-client #3728)

[codecov]

Codecov Report

Merging #3739 (0257ccc) into main (de354db) will decrease coverage by 0.02%.
The diff coverage is 83.33%.

❗ Current head 0257ccc differs from pull request most recent head 93c2ef3. Consider uploading reports for the commit 93c2ef3 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3739      +/-   ##
==========================================
- Coverage   93.45%   93.43%   -0.02%     
==========================================
  Files         290      290              
  Lines        8845     8849       +4     
  Branches     1834     1834              
==========================================
+ Hits         8266     8268       +2     
- Misses        579      581       +2     

Impacted Files	Coverage Δ
...etry-sdk-node/src/TracerProviderWithEnvExporter.ts	97.56% <83.33%> (-1.16%)	⬇️

... and 1 file with indirect coverage changes

[Flarna]

• The sdk-node package is deprecated

Really?

[pichlermarc]

• The sdk-node package is deprecated

Really?

Ah, yes, that's not true. Fixed in the description. It looks like my brain just won't operate properly today 🧠 🙅

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pichlermarc / name: Marc Pichler (921900f, fc3128a, 25b34ba, 13ee66b, f047829)
• ✅ login: web-flow / name: GitHub Web Flow (25b34ba, f047829)

[pichlermarc]

/easycla

[dyladan]

Jaeger doesn't show thrift as deprecated in their docs https://www.jaegertracing.io/docs/next-release/apis/

I thought it was deprecated so maybe their docs are just not updated. If the thrift is deprecated then I think this is fine. If they are still planning to use it into the future, we may want to consider a solution which supports it better in all environments.

[pichlermarc]

Jaeger doesn't show thrift as deprecated in their docs jaegertracing.io/docs/next-release/apis

I thought it was deprecated so maybe their docs are just not updated. If the thrift is deprecated then I think this is fine. If they are still planning to use it into the future, we may want to consider a solution which supports it better in all environments.

I do not think that thrift will be deprecated anytime soon, so I think adding more permanent support would be reasonable. 🙂 For now this PR will fix the problem outlined in #3521 for anyone who does not wish to use the JaegerExporter, but still runs into that problem due to how it is always required in the @opentelemetry/sdk-node package.

I created a feature-request issue to add more permanent support for this: #3752

[dyladan]

LGTM but i think the changelog can be more user-focused

[dyladan]

Lint failure is just rate limiting on github from link checking