* Migrate from CircleCI to GitHub Actions #115

* Move codecov to a separate job, disable jdk 11,13 for a moment #115

* Fix caching actions #115

* Reorder tasks, add badge #115

Support both .graphqls and .graphql

Add extensions-related properties to Maven/Gradle plugins #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

* Fix mainClassName in gradle examples

* Add example of GraphQL mutation request #75

* Fix CI config

* Extend and enhance README.md #37

* Fix README.md #37

* Add generateDataFetchingEnvironmentArgumentInApis to README.md #37

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

* Improve project structure #43

* Improve project structure #43

* Configs in "graphqlSchemas" should be optional #51

* Add missing file #43

* Fix module name #43