Closes gh-1262

As of gh-1117, the `HttpSyncGraphQlClient` supports the "GraphQL over
HTTP" specification. More specifically, it now handles HTTP 4xx
responses sent by GraphQL servers when the response content type is
"applcation/graphql-response+json".

This change introduced a regression where 4xx and 5xx HTTP responses now
always throw `HttpClientErrorException` (instead of throwing
`HttpClientErrorException` or `HttpServerErrorException` depending on
the case), and this exception is missing the response body and other
information from the response.

This commit ensures that exceptions are thrown in a similar fashion to
the default `StatusHandler` from Framwork.

Fixes gh-1259

As of gh-1163, the `GraphQlArgumentBinder` can bind using both a
constructor and setters. This is especially useful for Kotlin data
classes. This change introduced a significant performance penalty for
large and deep data sets.

This commit ensures that we are only performing setter binding for input
data that was not already consumed during the constructor binding phase.

Fixes gh-1284

This commit ensures that `PropertySelection` supports NonNull wrapper
types like `BookConnection!` when inspecting property paths for
connection edges and nodes.

Fixes gh-1298

Prior to this commit, a schema declaring a `BookConnection` nullable
type would decorate the relevant data fetcher and return an
`EMPTY_CONNECTION` value (a full Connection instance with empty nodes
and edges) if the original DataFetcher returns `null`.

This is unexpected for applications because the type is declared as
nullable in the schema and the application returns a `null` value.

This commit ensures that `EMPTY_CONNECTION` is only returned as a value
if the Connection type is marked as non nullable, `BookConnection!`.

This change should only affect applications with custom pagination
support, as Spring Data never returns `null` for empty pages.

Closes gh-1295

This commit adds support for Kotlin Value classes when binding arguments
to `@SchemaMapping` methods.
Complete Framework support is not available yet, but this change unlocks
typical Kotlin usage in GraphQL applications.

Closes gh-1186

Closes gh-1306

Closes gh-1307

Closes gh-1308

Closes gh-1309

Closes gh-1310