Version pinning for tracing and tracing-core

[lalitb]

Fixes: #2373

Changes

Pinning versions of tracing and tracing-core that are compatible with the version required to support name metadata in macros.

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.4%. Comparing base (fbc3c70) to head (1e48685).
Report is 391 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #2418   +/-   ##
=====================================
  Coverage   79.4%   79.4%           
=====================================
  Files        122     122           
  Lines      21708   21708           
=====================================
  Hits       17255   17255           
  Misses      4453    4453           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cijothomas]

We need this particular version for internal logging only right? The appender can operate with "0.1" itself. Wondering if we should use separate ones for these, instead of forcing even appender to 0.1.40?

Not a blocker anyway as 0.1.40 is already an year old.

[cijothomas]

Please add changelog entry before merge
Also left a non blocking question/comment.

[lalitb]

Please add changelog entry before merge Also left a non blocking question/comment.

updated changelog. Regarding appender, I believe it can work at version 0.1. However things would be bit complex once we add otel internal logging in appender. Let me check if we can conditionally use the proper tracing version in appender as separate PR.