Introduce new configs: typeResolverPrefix, typeResolverSuffix, generateModelsForRootTypes #206 (#207)

* Run GitHub workflows for develop branch

* Introduce new configs: typeResolverPrefix, typeResolverSuffix, generateModelsForRootTypes #206

* Fix some sonar issues

* Generate Response class having response data with exact type #159

* Extend GraphQLResultTest

* Support of parametrized fields in ResponseProjection #153

* Add support of Gradle/Maven plugins + tests #153

* Remove redundant classes

* Update README.md #153

* Introduce config to define parent interface for Query/Mutation/Subscription apis #135

* Gradle support for parent interfaces config #135

* Maven support for parent interfaces config #135

* Add README for parentInterfaces config #135

* Add navigation in README files

* Use upper bounded wildcard for interface methods returning list #145

* Delete Foo1.java.txt

* Delete Bar1.java.txt

* Delete Foo.java.txt

Add extensions-related properties to Maven/Gradle plugins #81

* Add more mapping configs for extensions resolvers #81

* More test coverage for MappingConfig #81

* Fix the order of resolvers definition logic #81

* Support extensions for all GraphQL types #81

* Performance improvement: scan definitions/extensions once #86

* Remove redundant methods from MapperUtils #86

* Fix plugin class names: Graphql -> GraphQL #86

* Fix test class name: GraphQLCodegenExtendTest #86

* Delete GraphqlCodegenExtendTest.java

Conceptually, GraphQL operations (queries/mutations/subscriptions) are a
special case of field resolvers that happen to be on well known root types.

Technically, this means that everything about field resolvers is the same
as these root types resolvers, apart from the fact that the former get an
instance of the resolved type as first param.

Therefore, all the configuration that applies to field resolvers also
applies to resolvers of the fields that are part of these root types, like
CompletableFuture return type, or DataFetcherEnvironment parameter.

Resolves: https://github.com/kobylynskyi/graphql-java-codegen/issues/64
Resolves: https://github.com/kobylynskyi/graphql-java-codegen/issues/61
Resolves: https://github.com/kobylynskyi/graphql-java-codegen/issues/63Co-authored-by: NJoffrey Bion <joffrey.bion@booking.com>

* Generate Builder for model classes #10

* Tests for MappingConfig #10

* Add Builder config to Maven/Gradle plugins #10

* More coverage for MappingConfig #10

* Fix CI config

* Introduce codegen for client code - Part 1. #37

* Remove redundant null-checks

* Minor fixes in Request class generation + improve code coverage. #37

* Customizable suffix of ResponseProjection classes. #37

* Code coverage for MappingConfig #37

* Fix method names #37 #53

* Support fields resolvers #25

* Code coverage for MappingConfig #25

This makes use of the MultiSourceReader provided by the graphQL library.
Using this reader allows to read a single document from multiple files,
while correctly associating line numbers and errors to their original
source file.

This doesn't bring any overhead because the method Parser.parseDocument(String) that was previously used already created a MultiSourceReader itself.
Note that the previous method didn't associate the source file name with the content used for parsing, while the new one does.

It allows to solve cross-reference problems with union types for instance.

Resolves:
https://github.com/kobylynskyi/graphql-java-codegen/issues/27Co-authored-by: NJoffrey Bion <joffrey.bion@booking.com>

* Cleanup imports/generics

* Remove residual trim() from previous PR

* Add utility function to compare file contents ignoring trailing whitespace
Co-authored-by: NJoffrey Bion <joffrey.bion@booking.com>

* Handle DirectiveDefinition in GraphQLDefinitionType determiner

* Adding a catch handler in case there are other types we can't handle

* Fixing typo from last commit