feat: add metric name translation strategy support for the Prometheus exporter

[herin049]

Description

Add support for specifying a name translation strategy for the Prometheus exporter as documented in: opentelemetry-specification

Fixes #5111
Depends on: #5123

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• 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?

uv run tox -e py314-test-opentelemetry-exporter-prometheus

Does This PR Require a Contrib Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

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

[MikeGoldsmith]

Looks great, thanks @herin049 🎉

[tammy-baylis-swi]

Thanks!

[github-actions]

This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment.
If you're still working on this, please add a comment or push new commits.

[herin049]

Small update on this PR, after going through the PR again and adding additional tests, I came to realize that the Python Prometheus client package (prometheus-client) automatically performs underscore escaping for metric names with seemingly no way to configure this behavior.

Likewise, there it also has the behavior of always appending the _total suffix to counters, and does not provide any easy way to control this behavior as well.

We will likely have to put this particular feature on hold until the required changes are made to the prometheus-client to include additional configurability mechanisms.