[chore][mysqlreceiver] Add stability level per metric

[ChrsMark]

Description

open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality.

We start by setting the stability of all metrics to development. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels.

Related to:

• Document SemConv compatibility requirements for components stability opentelemetry-collector#11878
• [mdatagen] Consider linking metrics/attributes from metadata.yaml to SemConv definitions opentelemetry-collector#13297
• [receiver/hostmetricsreceiver] semantic conventions transition #35325
• Add stability level per metric #42809

Link to tracking issue

Fixes ~

Testing

~

Documentation

Updated

[codeboten]

Not sure if this is desirable for development, but if a from version is set, the description for the metric will also include a message to give end users more information in the telemetry being emitted

[ChrsMark]

Not sure if this is desirable for development, but if a from version is set, the description for the metric will also include a message to give end users more information in the telemetry being emitted

That's reasonable. If we end up making mdatagen to require stability for new metrics, we can add an extra check to require the from for levels that are beyond development.

I will add this in the mdatagen to-dos.

edit: ref -> open-telemetry/opentelemetry-collector#13910

[atoulme]

@antonblock @ishleenk17 please review

[ishleenk17]

Looks good!