Deprecate the otlpmetric/internal package and sub-packages

[MrAlias]

The plan is to remove this package after this has been released.

Part of #3846

[pellared]

I think we should also deprecate exporters/otlp/otlpmetric package and module and add version.go to both otlpmetrichttp and otlpmetricgrpc modules. I would rather do it in a separate PR.

[MrAlias]

I think we should also deprecate exporters/otlp/otlpmetric package and module ...

Will this cause issues for users if there are sub-modules and sub-packages that are not deprecated?

and add version.go to both otlpmetrichttp and otlpmetricgrpc modules.

SGTM. We should also do the same for the otlptrace exporters.

I would rather do it in a separate PR.

👍

[codecov]

Codecov Report

Merging #4420 (fbf89ee) into main (6631519) will increase coverage by 0.0%.
Report is 1 commits behind head on main.
The diff coverage is 100.0%.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #4420   +/-   ##
=====================================
  Coverage   83.5%   83.5%           
=====================================
  Files        229     229           
  Lines      18679   18679           
=====================================
+ Hits       15605   15607    +2     
+ Misses      2755    2753    -2     
  Partials     319     319           

Files Changed	Coverage Δ
exporters/otlp/internal/config.go	100.0% <ø> (ø)
exporters/otlp/internal/retry/retry.go	98.3% <ø> (ø)
exporters/otlp/otlpmetric/internal/exporter.go	67.2% <ø> (ø)
...orters/otlp/otlpmetric/internal/oconf/envconfig.go	92.0% <ø> (ø)
...xporters/otlp/otlpmetric/internal/oconf/options.go	79.8% <ø> (ø)
exporters/otlp/otlpmetric/internal/otest/client.go	96.8% <ø> (ø)
...orters/otlp/otlpmetric/internal/otest/collector.go	6.8% <ø> (ø)
exporters/otlp/otlptrace/exporter.go	66.6% <100.0%> (ø)

... and 1 file with indirect coverage changes

[pellared]

Will this cause issues for users if there are sub-modules and sub-packages that are not deprecated?

AFAIK it should not cause any problem. Anyway verifying on a "test" repository would be safer than trusting me 😉

Still I think the PR can be merged as it is.