Global error handler cleanup - Jaeger Propagator

[lalitb]

Fixes #
Design discussion issue (if applicable) #

Changes

Please provide a brief description of the changes here.

Merge requirement checklist

• CONTRIBUTING guidelines followed
• Unit tests added/updated (if applicable)
• Appropriate CHANGELOG.md files updated for non-trivial, user-facing changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.5%. Comparing base (f3be05b) to head (a82d246).
Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #2250   +/-   ##
=====================================
  Coverage   79.5%   79.5%           
=====================================
  Files        121     121           
  Lines      20944   20950    +6     
=====================================
+ Hits       16667   16672    +5     
- Misses      4277    4278    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cijothomas]

Use Warning/Info instead of Error severity.
https://github.com/open-telemetry/opentelemetry-rust/pull/2250/files#r1817682423

[cijothomas]

I haven't followed the entire code path, so unclear what is the impact of this Warning. For eg: if an end users see this log entry, what should they be doing?
For all user facing logs, we should be very clear about the impact of this - will a span be dropped? will a span be using different parent ? will a span be created as root span? will we just ignore the header for tracestate and baggage too? or just ignore the traceparent header? something else?

I am not saying this should be fixed in this PR, as these are existing issues, nothing newly introduced in this PR. Since Metrics, Logs are where we are actively working towards Stable, we can probably merge this now, and come back when we start working towards Tracing Stable release?

[cijothomas]

I do have some concerns about whether the logs are actionable/informative enough for end users - https://github.com/open-telemetry/opentelemetry-rust/pull/2250/files#r1817692142

But I don't think this should be a blocker now, as Tracing signal is unlikely to be in stable state soon. (For Metrics, Logs, we need to make sure every log is informative/actionable, as it is getting closer to stable release now)