[federation] add support for Fed 2.1 (ExpediaGroup#1591)

By default, Supergraph schema excludes all custom directives. Federation 2.1 adds new `@composeDirective` that can be used to instruct composition logic to preserve custom directives in the Supergraph schema.

```graphql
directive @composeDirective(name: String!) repeatable on SCHEMA
```

ktlint fix - unused import (ExpediaGroup#1594)

[federation] fix override directive definition (ExpediaGroup#1554)

`@override` directive is not repeatable. Fixing copy and paste bug.

feat: DataFetchingEnvironment extensions to access to entries in Grap…

…hQLContext (ExpediaGroup#1552) (ExpediaGroup#1553)

* feat: DataFetchingEnvironment extensions to access to data in GraphQLContext

* feat: add copyright

[federation] use federation-jvm ServiceSDLPrinter (ExpediaGroup#1546)

Updated `FederatedSchemaGeneratorHooks` to use `ServiceSDLPrinter` provided by the `federation-jvm` in favor of our custom printer logic.

Make nullable parameters always optional (ExpediaGroup#1528)

* Make nullable parameters always optional

Treat nullable parameters that have no default value as if their default
was set to null.

Nullable parameters that have a default value explicitly set will
continue to use that as their default.

* Apply review feedback

- add KParameter.isNotOptionalNullable()
- minor cleanups in mapToKotlinObject

feat: mark execution result and Throwable as nullable (ExpediaGroup#1521

)

feat: update graphql-java 19.1 (ExpediaGroup#1519)

* feat: update graphql-java 19.1

* feat: graphql java directive skip removed unneded quote

Co-authored-by: samvazquez <[email protected]>

[build] update to latest dependencies (ExpediaGroup#1495)

### 📝 Description

Update to the latest dependencies. 

Fixed duplicate publication from `graphql-kotlin-gradle-plugin` - this was a warning before but latest version of `com.gradle.plugin-publish` treats it as a failure

NOTE: I did not update project to Kotlin v1.7 as I think that as a library we should target older version to allow for largest adoption.

### 🔗 Related Issues

[client] support non JSON primitive scalars (ExpediaGroup#1488)

Update `kotlinx-serialization` handling of custom scalars to allow non-primitive values. While custom scalars are most often represented as some primitive value (e.g. UUID -> String), there are use cases when scalars need to be represented as objects. One common use case is Apollo Federation and its usage of `_Any` scalar to represent arbitrary entity object map that contains various fields to uniquely identity it.

Updated custom scalar documentation with examples  n how to use arbitrary objects as custom scalars.

Resolves:

* ExpediaGroup#1408
* ExpediaGroup#1435
* ExpediaGroup#1445