Add new Blazor metrics for Net10

[pavelsavara]

Changes

Adding new metrics for Blazor UI framework

Related PR
dotnet/aspnetcore#61609

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.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pavelsavara / name: Pavel Savara (92f860b, 278c73a, 7c9f4b7, 388171d, bb47309, 5142761, 317def2, 39b8440)

[lmolkova]

yes, check out https://github.com/open-telemetry/semantic-conventions/blob/main/CONTRIBUTING.md#2-update-the-markdown-files and you can use other md files as examples, e.g.

semantic-conventions/docs/dotnet/dotnet-aspnetcore-metrics.md

Line 35 in 86cad42

<!-- semconv metric.aspnetcore.routing.match_attempts -->

we don't have it yaml (yet), but we should document recommended boundaries for histograms - e.g. like here https://github.com/open-telemetry/semantic-conventions/blob/main/docs/dotnet/dotnet-http-metrics.md#metric-httpclientrequesttime_in_queue

[pavelsavara]

I'm doing something wrong

pavelsavara@SAVARA-DESKTOP:~/dev/semantic-conventions$ make table-generation attribute-registry-generation
docker run --rm \
        -u 1000:1000 \
        --mount 'type=bind,source=/home/pavelsavara/dev/semantic-conventions/templates,target=/home/weaver/templates,readonly' \
        --mount 'type=bind,source=/home/pavelsavara/dev/semantic-conventions/model,target=/home/weaver/source,readonly' \
        --mount 'type=bind,source=/home/pavelsavara/dev/semantic-conventions/docs,target=/home/weaver/target' \
        docker.io/otel/weaver:v0.16.1@sha256:5ca4901b460217604ddb83feaca05238e2b016a226ecfb9b87a95555918a03af registry update-markdown \
        --registry=/home/weaver/source \
        -Dregistry_base_url=/docs/registry/ \
        --templates=/home/weaver/templates \
        --target=markdown \
        --future \
        /home/weaver/target
ℹ No registry manifest found: /home/weaver/source/registry_manifest.yaml

Diagnostic report:

invalid_semconv_group

  × The following YAML snippet does not match any of the allowed schemas
  │ (anyOf, see help section).
  help: Specifies the stability of the semantic convention. Note that, if
        stability is missing but deprecated is present, it will automatically
        set the stability to deprecated. If deprecated is present and
        stability differs from deprecated, this will result in an error.

[lmolkova]

/ cc @semconv-dotnet-approver @stevejgordon @martinjt

[pavelsavara]

@lmolkova thanks for your time and feedback, appreciated.

Let's move naming discussion back the other PR to where there are the rest of the stakeholders, so we don't have to duplicate the same explanations twice.

I will update this PR once we reach conclusion there. I will also add more links and explanations later.