patch: Increase support of harder to detect `gql.tada` API usage patterns

[!NOTE] Marking this as a minor since we already have minor changes queued up and some of the API signatures have changed slightly.

Summary

This aims to reduce the amount of separate templates.has based checks and introduce a new check that can also detect gql.tada via the TypeChecker as a fallback if the name (or expression) of graphql() calls is non-standard.

Set of changes

Add checks.ts for all predicates
Detect graphql() calls by checking !!graphql.scalar and !!graphql.persisted via the typ e checker
- This works even if graphql itself is not an identifier (any expression)
- This works even if graphql is renamed (more relevant now due to multi-schema support)
Detect graphql.persisted() calls with the above logic
Extract logic to detect GraphQL calls and GraphQL tagged template literals
- Also unifies checks for templates.has into few reusable function
Fix several branches where GraphQL tags were checked for even if isCallExpression was truthy
Widen NoSubstitutionTemplateLiteral to StringLiteralLike
- graphql('...') and graphql("...") will work now
- NOTE: I chose not to implement a TypeChecker based approach here for arguments[0] or arguments[1] yet, but this could lead to some refactors which might slim down the codebase
Prevent getAllFragments from expanding to check for fragments via declarations (graphql-code-generator code branch) even if gql.tada is active with new isTadaGraphQLCall check
Extract logic to resolve graphql() fragments array literal argument
- Expand to support as const
- Consistently resolve PropertyAccessExpressions

0no-co / GraphQLSP

patch: Increase support of harder to detect `gql.tada` API usage patterns #309

Summary

Set of changes

🦋 Changeset detected