[client] support @include and @Skip directives (ExpediaGroup#1341)

[generator] add runtime warning on deprecated context usage (ExpediaG…

…roup#1323)

### 📝 Description
This PR updates `FunctionDataFetcher` so that it logs a warning when injecting a `GraphQLContext`.  This functionality is [deprecated](https://github.com/ExpediaGroup/graphql-kotlin/blob/master/website/docs/schema-generator/execution/contextual-data.md#interface-injection-deprecated).  Unlike the `GraphQLContext` interface itself, which is annotated `@deprecated, there is no compile or runtime time warning when using `GraphQLContext` interface injection in a query or mutation.

### 🔗 Related Issues
* discussion: ExpediaGroup#1305
* supersedes: ExpediaGroup#1306

Co-authored-by: Joel Brown <jbrown@classpass.com>

[dependencies] downgrade to graphql-java 17.2 (ExpediaGroup#1317)

Support creating the new context map (ExpediaGroup#1292)

* Support creating the new context map

* Fix subscription hooks

* Update docs and deprecation notice

* Use inline builder

* Update unit test docs

* Use default context map in subscriptions test

* Undo public arg name changes

Improve errors for unions (ExpediaGroup#1273)

Dependency update (ExpediaGroup#1264)

* Dependency update

* Jackson matching spring version

* Update gradle.properties

* Update manual kotlin versions

* Update other hardcoded versions

Test scalar converters with Ulocale (ExpediaGroup#1259)

* Test scalar converters with Ulocale

* Update wiremock schema

* Add fields to types

[build] dependency updates (ExpediaGroup#1253)

* [build] dependency updates

Updates to the latest version of the libs.

This change does not include Kotlin update to 1.5.30 due to following issues:
* Gradle Kotlin compile task presents a warning that Java compile task (we don't have any Java sources) uses different JVM target (Java version defaults to your local JVM default)
* Above warning can be fixed by explicitly configuring Java tasks (again we don't have any Java sources) to use Java 8 target OR through toolchain configuration - at least it should be, when using toolchain configuration `kapt` blows up with unable to find the toolchain JVM
* Android test project used as an integration test for Gradle plugin blows up with `Cannot have abstract method KotlinJavaToolchain.getJdk()`

* fix unit tests
`OptionalInput` is now supported for both kotlinx-serialization and Jackson. Updating test to account for this.

Backport GraphQLUnion to 4.x.x (ExpediaGroup#1234)

[plugin] support android compile targets (ExpediaGroup#1231)

* [plugin] support android compile targets

Default (JVM) build use `compileKotlin`/`compileTestKotlin` tasks. Android builds use variants which has their own targets (e.g. `compileDebugKotlin`). Since our tasks are finalized by the compile tasks we cannot apply it on android builds as default JVM tasks dont exist.

* fix compile dependency

Gradle scans all decorated plugin/tasks/extensions classes to find all the injection points, apply validations etc. This means that we cannot have any method signatures in the plugin code that references compile only dependencies. Simple fix is to move the affected code to a separate file. See: gradle/gradle#8411 for details.

* fix android build dependency

* parameterize android plugin version