Fix Core::Telemetry stacktrace and error logging

[Strech]

What does this PR do?

Correct internal Telemetry logging stacktrace and error name reporting.

Motivation:

Without that change stacktrace doesn't show up correctly which also leads to ErrorTracking being impossible. In addition an extra space added between Error name and description.

Change log entry

No.

Additional Notes:

How to test the change?

CI and ErrorTracking example

[datadog-datadog-prod-us1]

Datadog Report

Branch report: fix-telemetry-error-reporting
Commit report: 66aec5f
Test service: dd-trace-rb

✅ 0 Failed, 22073 Passed, 1457 Skipped, 5m 37.59s Total Time

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.76%. Comparing base (b6fe8c0) to head (66aec5f).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4220   +/-   ##
=======================================
  Coverage   97.76%   97.76%           
=======================================
  Files        1357     1357           
  Lines       82130    82131    +1     
  Branches     4174     4174           
=======================================
+ Hits        80292    80293    +1     
  Misses       1838     1838           

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

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-12-11 15:22:35

Comparing candidate commit 66aec5f in PR branch fix-telemetry-error-reporting with baseline commit b6fe8c0 in branch master.

Found 1 performance improvements and 0 performance regressions! Performance is the same for 30 metrics, 2 unstable metrics.

scenario:profiler - sample timeline=false

• 🟩 throughput [+0.507op/s; +0.518op/s] or [+8.390%; +8.584%]

[p-datadog]

I believe I need this fix for DI as well, therefore I will be able to test it once it's merged.

I approve the diff but does this PR really not need a change log entry?

[Strech]

I approve the diff but does this PR really not need a change log entry?

Yes, it doesn't. It's an internal Telemetry logger and it's not customer facing code. It's easy to confuse with OpenTelemetry, but it's a different beast.