feat(attributes): Add graphql.processing.type

[andreiborza]

Description

Adds graphql.processing.type, which says which part of GraphQL request processing a span represents: parse, validate, execute, resolve and so on. Adds it to the graphql span name templates as well, so the phases get a name of their own:

GraphQL {{graphql.operation.type}}
GraphQL {{graphql.processing.type}}
GraphQL Operation

GraphQL span names are low cardinality and carry the operation type at most, so a parse span and a validate span are otherwise indistinguishable. A parse span carries no GraphQL attribute at all today.

Both attributes are set on an operation span, and only graphql.processing.type on the phases, so the template order keeps GraphQL query for operations and gives GraphQL parse / GraphQL validate / GraphQL resolve to the rest.

Also replaces the mutation and query examples, which no template can produce since Sentry prefixes GraphQL span names with GraphQL , as the otel_notes on the same entry says. They predate that prefix.

The attribute name and its value list follow the GraphQL OpenTelemetry Working Group proposal in open-telemetry/semantic-conventions#3515. That PR is still a working draft, so is_in_otel is false for now and should be flipped once it lands upstream. Note that the working group deliberately did not widen graphql.operation.type for this, since that attribute holds the GraphQL operation type (query, mutation, subscription) and applies only to spans that run an operation.

@sentry/javascript wants this for getsentry/sentry-javascript#23542, where streamed GraphQL spans lose the operation name and the resolver field path from their names.

PR Checklist

• I have run yarn test and verified that the tests pass.
• I have run yarn generate to generate and format code and docs.

If an attribute was added:

• The attribute is in a namespace (e.g. nextjs.function_id, not function_id)
• I have used the correct value for apply_scrubbing (i.e. manual or auto. Use never only for values that should never be scrubbed such as IDs)

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• (attributes) Add graphql.processing.type by andreiborza in #572

Bug Fixes 🐛

• (names) Correct graphql span name examples by andreiborza in #573

---

_{🤖 This preview updates automatically when you update the PR.}

[Lms24]

attribute and name changes look good to me. IMHO these are all low-cardinality and the processing types were previously missing and would have caused us to fall back to the static string. So having this new rule should be fine.