feat: kotlinx serialization for GraphQLServerRequest

[samuelAndalon]

📝 Description

Switch from jackson to kotlinx.serialization for serialization/deserialization of GraphQLServerRequest types.

After running benchmarks we where able to identify that deserializing GraphQLServerRequest with kotlinx.serialization is quite faster than doing it with jackson, the reason ? possibly because jackson relies on reflections to identify deserialization process.

On the other hand, serialization/deserialization of GraphQLServerReponse type is still faster if done with jackson, possibly because of how kotlinx.serialization library was designed and the poor support for serializing Any type:
Kotlin/kotlinx.serialization#296, which causes a lot of memory comsumption.

As part of this PR also including the benchmarks. For that, i created a separate set of types that are marked with both jackson and kotlinx.serialization annotations.

Benchmarks results:
Executed on a MacBookPro 2.6 GHz 6-Core Intel Core i7.

GraphQLServerRequest Deserialization

GraphQLBatchRequest
4 batched operations, each operation is aprox: 30kb

GraphQLRequest

GraphQLServerResponse Serialization

GraphQLBatchResponse

GraphQLResponse

[samuelAndalon]

Important to mention that Ktor server will still use jackson as engine for deserialization:
https://github.com/ExpediaGroup/graphql-kotlin/blob/master/servers/graphql-kotlin-ktor-server/src/main/kotlin/com/expediagroup/graphql/server/ktor/GraphQLRoutes.kt#L70

Spring webflux server will use kotlinx as if server detects both set of annotations jackson, kotlinx, will use kotlinx.

In a separate PR we can make this configurable.