[mdatagen] Resource attributes should be able to define their stability level

[ChrsMark]

Component(s)

cmd/mdatagen

Describe the issue you're reporting

We should allow resource attributes to define their stability similarly to metrics and others: https://github.com/open-telemetry/opentelemetry-collector/blob/main/cmd/mdatagen/metadata-schema.yaml#L159-L185

#14646 added support for linking attributes to semantic conventions of OTel. It would be nice to be able to define the stability level explicitly too.

/cc @osullivandonal @dmitryax

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners:

• cmd/mdatagen: @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[dmitryax]

Sounds reasonable to me

[highlyavailable]

I would like to take this on! A few things I want to check before I start,

For the stability field, would it be best to hve the same shape as metrics.stability (<development|alpha|beta|stable|deprecated> enum + the optional deprecated: {since, note} block), or the telemetry.metrics.stability object form ({level: [alpha|stable|deprecated], from})?

Also, I think the field would should be optional without default, so tht all the existing metadata.yaml files across collector+contrib remain valid, or default to beta