[service] implement a noop tracer provider

[codeboten]

This is to address some of the memory concerns around the SDK's noop tracer provider. Instead of using the published noop tracer provider, we implement our own to avoid the cost of context propagation, which has been proven to be high enough to cause issues for end users.

Part of #10858

[mx-psi]

Is there any upstream issue about the

memory concerns around the SDK's noop tracer provider

?

[codeboten]

Is there any upstream issue about the

I attended the go SIG on 28-Aug-2024, and the end result of the discussion was that because the no-op tracer still has to propagate context, the proposed solution if we need an alternative was to implement our own no-op tracer provider.

[codecov]

Codecov Report

Attention: Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.

Project coverage is 92.20%. Comparing base (3612194) to head (c60c2d9).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
service/telemetry/tracer.go	20.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11026      +/-   ##
==========================================
- Coverage   92.21%   92.20%   -0.02%     
==========================================
  Files         405      405              
  Lines       19240    19244       +4     
==========================================
  Hits        17743    17743              
- Misses       1130     1134       +4     
  Partials      367      367              

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