Update build-tools to 0.24.0

[lmolkova]

Fixes #807

For the purpose of code review: Please review YAML changes - markdown files are autogenerated

Changes

• update build-tools version to the next one (0.24.0 unreleased)
• Adds stability to enum members
• Add stability to a few experimental + deprecated attributes

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

[lmolkova]

Dear codeowners, please review md and yaml files in your area

Changes to pay special attention to:

• all auto-generate attributes and metrics tables should have Stability column with a badge - make sure it matches your expectations.

Cosmetic changes:

• Ordering now takes requirement level into consideration
• Requirement Level is rendered slightly differently than before

[joaopgrassi]

Can we run the tools and tackle each change in a separated PR? For example the sorting now changes a lot of things and it makes it hard to see what actually is a change vs what is just "cosmetic". I think that will make the review process easier.

[lmolkova]

Can we run the tools and tackle each change in a separated PR? For example the sorting now changes a lot of things and it makes it hard to see what actually is a change vs what is just "cosmetic". I think that will make the review process easier.

Great idea, but it'd only be possible if I manually handcrafted each change. We wouldn't be able to merge them because the md check would fail.
I think going forward we should release build-tools more (maybe each substantial md change) so that we don't have enormous diffs.

[jsuereth]

For the purpose of code review:

1. Please review YAML changes
2. Please ensure conflicts in Markdown are ok, but you can ignore the autogenerated portion as that's based on the tool.

[lmolkova]

//cc @open-telemetry/semconv-mobile-approvers @open-telemetry/semconv-system-approvers @open-telemetry/semconv-jvm-approvers @open-telemetry/semconv-k8s-approvers @open-telemetry/semconv-container-approvers @open-telemetry/semconv-http-approvers @open-telemetry/semconv-dotnet-approver

could you please review the yaml file changes for your area? Thanks!

[joaopgrassi]

Thank you for working on this! It's a big milestone 🚀

[trisch-me]

this is awesome!

[ChrsMark]

LGTM

[lmolkova]

@jack-berg @trask @jonatan-ivanov @mateuszrzeszutek could you please check JVM-related yaml changes in this PR? 👍

[lmolkova]

@JamesNK @noahfalk @antonfirsov could you please check dotnet-related yaml changes in this PR?

[lmolkova]

@nachoBonafonte @LikeTheSalad @bryce-b @breedx-splk @surbhiia could you please check mobile-related yaml changes in this PR?

[joaopgrassi]

Sorry for the conflicts, I somehow forgot we were waiting for this 🙈. Got a bit too excited in moving things to the registry 😅

[jack-berg]

JVM stuff looks good to me.

[noahfalk]

dotnet-aspnetcore.yaml, dotnet-kestrel.yaml, and dotnet-signalr.yaml all look fine to me. Were there any other files that are applicable to dotnet?

[lmolkova]

@noahfalk this should be it. Thank you!

[breedx-splk]

model/logs/mobile-events.yaml and mobile/events.md both look good to me. 👍🏻