feat: pass graphQLContext to KotlinDataLoaderRegistryFactory

[samuelAndalon]

📝 Description

passing graphQLContext instance from GraphQLRequestHandler to KotlinDataLoaderRegistryFactory.generate to allow DataLoaders to easily pass it as context of the BatchLoaderContext, and free up the context by key.

🔗 Related Issues

resolves #1752

[smyrick]

You could take the Apollo Server approach and now that the graphql-java context is just a map, you could let library users save their own data loaders into the context and fetch them. Then you could just delete the KotlinDataLoader class altogether

[samuelAndalon]

You could take the Apollo Server approach and now that the graphql-java context is just a map, you could let library users save their own data loaders into the context and fetch them. Then you could just delete the KotlinDataLoader class altogether

internally the DataLoaderRegistry is actually stored in the GraphQLContext, thats how data fetchers/resolvers can access to it through the DataFetchingEnvironment, KotlinDataLoader is a convenient way to allow users to register data loaders and let the server do the work of creating the registry and adding them to the context.