Add new GraphQL query InfrahubGraphQLQueryReport

[ogenstad]

Why

New GraphQL query to make it easier for end users to figure out how the GraphQLQueryAnalyzer views a query (for artifact regeneration).

This will later be used by infrahubctl graphql query-report (note that PR works together with this mutation but the PR itself hasn't been reviewed by me it's just some generated code which I'll get back to once this is merged to stable. Then after the next patch release of Infrahub I'll get back to the SDK PR and create some integration tests for it as well and potentially clean up that code. Once that is done I'll also remove the SpecKit files generated here.

What changed

• Relevant changes are in backend/infrahub/graphql/queries/graphql_query_report.py, where we add a new GraphQL query called InfrahubGraphQLQueryReport, it produces a report based on the contents of a GraphQL query, as it is now the only field is targets_unique_nodes which indicates if the query can be used for artifact definitions and able to target a single unique base node. (In the future we can add stuff like models being queried along with attributes and relationships) Perhaps the permissions that would be required to run the query. The types of relationships it traverses, if fragments etc are used and the complexity of the query. But for now it's only a single field.
• Added a number of tests for this new mutation.

[codspeed-hq]

Merging this PR will not alter performance

✅ 12 untouched benchmarks

---

_{Comparing ifc-2504-graphql-query-report (540653c) with stable (12a5b15)}

[ogenstad]

The reason we have this here is to avoid test setups between each test case.

[ogenstad]

Note I tried a different approach here to avoid having to have # noqa: ARG003 comments. This is an argument that Graphene adds that we never and up using. So something we could perhaps transfer to other places as well..