feat(prometheus): update prometheus exporter with wip metrics sdk

[legendecas]

Which problem is this PR solving?

Fixes Partially #2773

This PR updates the Prometheus Exporter to the latest Metrics SDK type definitions.

• We may need to split the necessary part of changes on sdk-metrics-base into separated PRs.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• PrometheusSerializer
• PrometheusExporter

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated

[codecov]

Codecov Report

Merging #2824 (f86947d) into main (da22673) will increase coverage by 0.40%.
The diff coverage is n/a.

❗ Current head f86947d differs from pull request most recent head 15b793b. Consider uploading reports for the commit 15b793b to get more accurate results

@@            Coverage Diff             @@
##             main    #2824      +/-   ##
==========================================
+ Coverage   93.06%   93.46%   +0.40%     
==========================================
  Files         150      162      +12     
  Lines        4713     5568     +855     
  Branches      994     1178     +184     
==========================================
+ Hits         4386     5204     +818     
- Misses        327      364      +37     

Impacted Files	Coverage Δ
...exporter-metrics-otlp-http/src/transformMetrics.ts	95.65% <0.00%> (ø)
packages/exporter-trace-otlp-http/src/util.ts	100.00% <0.00%> (ø)
...s/opentelemetry-instrumentation-fetch/src/fetch.ts	97.00% <0.00%> (ø)
...s/exporter-trace-otlp-http/src/OTLPExporterBase.ts	100.00% <0.00%> (ø)
...ry-exporter-prometheus/src/PrometheusSerializer.ts	95.12% <0.00%> (ø)
...ation-xml-http-request/src/enums/AttributeNames.ts	100.00% <0.00%> (ø)
...etry-exporter-prometheus/src/PrometheusExporter.ts	93.42% <0.00%> (ø)
...-instrumentation-fetch/src/enums/AttributeNames.ts	100.00% <0.00%> (ø)
...mentation-xml-http-request/src/enums/EventNames.ts	100.00% <0.00%> (ø)
...emetry-instrumentation-xml-http-request/src/xhr.ts	97.57% <0.00%> (ø)
... and 2 more

[aabmass]

I didn't see anything in the code, but do you do anything with unit? In the python exporter, we use the official prometheus client library to generate text format and it actually accepts the unit and concatenates it into the metric name. Example test case.

I know there is a current spec effort to document OTLP<->Prometheus conversion, but it doesn't say anything about unit right now. Thoughts?

Update: found this in the prometheus docs. I will check with my coworker who's working on the OTLP to prom spec to see if this should be officially added.

[dyladan]

LGTM it's really a lot less change than I thought would be needed.

[dyladan]

After the OTLP exporters are updated we should remove wip from all names and have a release

[dyladan]

No need to change the name here I think. The package is private and nothing depends on it.

[legendecas]

Reverted :)

[dyladan]

No need to change the name here I think. The package is private and nothing depends on it.