feat(api): merge api-metrics into api

[legendecas]

Which problem is this PR solving?

Merge stable API packages @opentelemetry/api-metrics into @opentelemetry/api.

Fixes #3368

Notably, those packages that depend on the metrics API now declare peer dependency on @opentelemetry/api ">=1.2.0 <1.3.0" and "^1.,2.0". The version range should be updated to ">=1.3.0 <1.4.0" and "^1.3.0" respectively when metrics API is released in @opentelemetry/api v1.3.0.

Type of change

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Tree-shaking tests in @opentelemetry/api.

Checklist:

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

[codecov]

Codecov Report

Merging #3374 (a1aeb33) into main (bdc603c) will decrease coverage by 0.02%.
The diff coverage is 98.50%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3374      +/-   ##
==========================================
- Coverage   93.26%   93.24%   -0.03%     
==========================================
  Files         246      247       +1     
  Lines        7413     7341      -72     
  Branches     1533     1509      -24     
==========================================
- Hits         6914     6845      -69     
+ Misses        499      496       -3     

Impacted Files	Coverage Δ
api/src/internal/global-utils.ts	90.62% <ø> (ø)
api/src/metrics/Metric.ts	100.00% <ø> (ø)
api/src/metrics/NoopMeter.ts	97.36% <ø> (ø)
api/src/metrics/NoopMeterProvider.ts	100.00% <ø> (ø)
...emetry-instrumentation-grpc/src/instrumentation.ts	75.86% <0.00%> (ø)
...ges/opentelemetry-instrumentation-http/src/http.ts	94.77% <ø> (-0.02%)	⬇️
...es/opentelemetry-instrumentation-http/src/utils.ts	99.17% <ø> (ø)
...entelemetry-instrumentation/src/autoLoaderUtils.ts	92.00% <ø> (ø)
...entelemetry-instrumentation/src/instrumentation.ts	69.23% <ø> (-1.14%)	⬇️
.../opentelemetry-sdk-metrics/src/aggregator/types.ts	100.00% <ø> (ø)
... and 30 more

[pichlermarc]

I think merging these packages is the right way to go 🙂
Looks good 🙂

[MSNev]

It would be nice to have this as explicit (named) exports rather than implicit exports (*) to remove the unexpected inclusion of exported values from the listed files.

[legendecas]

I have updated the exports in *-api.ts file to be explicit so I export everything from *-api.ts from index.ts. Like trace-api.ts, which used to be export * from each internal module.

In this way, we can have a relatively short index.ts and check *-api.ts for the exports of each API.

[dyladan]

I agree with @MSNev here. The index is the one source of truth to see what is exported from the API package. It is not convenient to have to go to another file to see what is exported. Also, someone may add an export to that file not realizing that index.ts has the * export.

[MSNev]

Left a few minor suggestions..

I REALLY like the removal of the namespace references api.xxx etc, this is one of the things I was planning for the web sandbox because of the tree-shaking improvements that this has.

[legendecas]

@MSNev @dyladan updated with explicit exports moved to index.ts. PTAL :)

[MSNev]

👍