Implement Otel Translation Strategies per spec

[ywwg]

ref: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk_exporters/prometheus.md#configuration

This will allow java users to enable NoTranslation mode for 1:1 otel metric names, if they so choose.

per the discussion on CNCF Slack, when we add documentation for this feature we should make sure to point out that modes without suffixes are technically in violation of the Open Metrics specification and may lead to unpredictable results. Example text for other warnings: https://github.com/prometheus/otlptranslator/blob/main/strategy.go#L25-L60

[fstab]

I'm not convinced that violating the spec is a great idea. This requires discussion, so I put it on the agenda of the Prometheus dev summit.

[zeitlinger]

I have created a PR that supports the OTel translation strategy - but does nothing more

• it doesn't prevent that _total is stripped from metric names, because OTel SDK is passing a snapshot where the the step of stripping suffixes is already done
• it only supports prometheus and OpenMetrics exposition formats, because OTel SDK only supports pull

Docs (and warnings) are not added yet.

[zeitlinger]

We decided to wait for OpenMetrics 2.0