OTLP metric export errors use a consistent error message prefix

[jmacd]

When a user configures both a tracing SDK and metrics SDK the, existing error-handling and logging mechanism do not indicate whether it is a tracing or a metrics failure. For SDKs and vendors that route metrics and traces to different services, it is important to indicate which of the two paths is experiencing problems.

Part of #3513.

[codecov]

Codecov Report

Merging #3515 (73bcf01) into main (bc5cf7e) will decrease coverage by 0.0%.
The diff coverage is 90.9%.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #3515     +/-   ##
=======================================
- Coverage   78.1%   78.1%   -0.1%     
=======================================
  Files        165     165             
  Lines      11809   11812      +3     
=======================================
+ Hits        9226    9228      +2     
- Misses      2387    2388      +1     
  Partials     196     196             

Impacted Files	Coverage Δ
exporters/otlp/otlpmetric/otlpmetrichttp/client.go	76.6% <0.0%> (ø)
exporters/otlp/otlpmetric/internal/exporter.go	70.6% <100.0%> (+3.4%)	⬆️
sdk/trace/batch_span_processor.go	80.2% <0.0%> (-1.8%)	⬇️
exporters/jaeger/jaeger.go	91.1% <0.0%> (+0.8%)	⬆️

[MrAlias]

Please fix the lint issues and add a changelog entry.

[jmacd]

Will reopen this PR following the discussion in #3516.

Apologies for not passing lint before sending the PRs. I see that the lint tools are working again (what with all the churn related to generics)!