Release v0.32.0 -- Revised Metric SDK (Alpha)

[MrAlias]

Part of #3176

Blocked by:

• Fix prometheus exporter panic on invalid metric #3182
• Release Preparation: Update host instrumentation to use new metric SDK opentelemetry-go-contrib#2754
• Release Preparation: Update runtime instrumentation to use new SDK opentelemetry-go-contrib#2756
• Release Preparation: Remove metric SDK use in otelhttp/test opentelemetry-go-contrib#2758
• Release Preparation: Update metric SDK use in otelgocql opentelemetry-go-contrib#2760
• Release Preparation: Temporarily remove metric SDK use in otelbeego/test opentelemetry-go-contrib#2762

[codecov]

Codecov Report

Merging #3184 (5f3f2a5) into main (fae4b90) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #3184   +/-   ##
=====================================
  Coverage   77.4%   77.4%           
=====================================
  Files        158     158           
  Lines      11084   11084           
=====================================
  Hits        8583    8583           
  Misses      2306    2306           
  Partials     195     195           

Impacted Files	Coverage Δ
exporters/jaeger/jaeger.go	90.3% <0.0%> (-0.9%)	⬇️
sdk/trace/batch_span_processor.go	81.9% <0.0%> (+0.8%)	⬆️

[MrAlias]

I didn't include a release for the OC bridge as it was removed and planned to be replaced in the next milestone. I think this is fine as the last release of the OC bridge should sill bring in the previous metric SDK code. Though, I'm not 100% this is the correct approach. Thoughts?

[MadVikingGod]

I'm ok with this approach. It might cause a bit of churn for anyone using the opencensus metrics bridge.

The only alternative I can think of is to not release a 0.32 of the bridge and wait until it's implemented (basically pin it at 0.31 and 1.9 until then).