feat(graphql_semantic): build semantic model from AST

[vohoanglong0107]

Summary

Depends on #3427

Build a Semantic model for GraphQL from AST.

Unlike in JS, in GraphQL, a variable can be referenced in a fragment, which in turn can be referenced by multiple operations, and then defined in those operations. This results in a variable being potentially defined in multiple locations.

fragment HeroDetails on Character {
    name(startWith: $start)
}

query HeroWithH($start: String = "H") {
	...HeroDetails
}

query HeroWithO($start: String = "O") {
	...HeroDetails
}

In this case, the $start variable is defined in both the HeroWithH and HeroWithO variable definitions, and referenced at (startWith: $start) in HeroDetails fragment.

To address this, each operation and fragment will be associated with a scope. The scope will keep track of every referenced fragment, allowing it to track every referenced variable, either directly referenced or indirectly through a referenced fragment. Then, it will try to bind every referenced variable to its declaration inside an operation definition.

Test Plan

All the calls to retrieve binding and reference should correctly return the respective bindings and references of the AST node.

[codspeed-hq]

CodSpeed Performance Report

Merging #3378 will improve performances by 6.45%

_{Comparing vohoanglong0107:feat-init-graphql-semantic (dfd03cd) with main (2ef23e7)}

Summary

⚡ 1 improvements
✅ 103 untouched benchmarks

Benchmarks breakdown

	Benchmark	main	vohoanglong0107:feat-init-graphql-semantic	Change
⚡	dojo_11880045762646467684.js[cached]	8.5 ms	8 ms	+6.45%

[ematipico]

Are you able to separate the changes you made to the parser from the actual model changes? Or are they connected? It doesn't seem they are by reading the description of the PR

[vohoanglong0107]

Ah sure

[ematipico]

This is great!

[ematipico]

This distinction was created for TypeScript, is it true for GraphQL too?

[vohoanglong0107]

Yeah, consider the following example:

query Query {}

type Query

schema {
  query: Query
}

Here Query is used both as the name of the query, and the type of query in the schema

[ematipico]

We recently refactored the JS semantic model to own u32, you should consider it

[ematipico]

Update the description