Adding the ability to provider custom GraphQLClient

[ngoctranfire]

Currently, we have the ability to provide 2 different scopes for schemas. However, this all generates our extensions to only the GraphQL Client. It would be great if we can specify which schemas belong to which GraphQL client and which functions belong to each individual client. For example,
Let's say I have two scopes:
scopes:
-graph1l/schema/graph_1.schema
-graph2l/schema/graph_2.schema

I should be able to set the client too, let's say I have Graph1Client (which extends GraphQLClient), and another Graph2Client.
In addition, we should be able to specify which client the schema and functions the GraphQL Client belongs to.

Not sure what is the best way to do it, but I think this would be a good addition!

[github-actions]

👋 @ngoctranfire
Thank you for raising an issue. I will investigate the issue and get back to you as soon as possible.
Please make sure you have provided enough context.

This library is created and maintained by me, @budde377. Please consider supporting my work and ensure our survival by donating here.

[budde377]

It is an interesting idea. The API works by extension methods that can extend any client. How would you provision the different clients?

[nocturnalflame]

@budde377 I think we can change it so that when someone adds "scope", they have to also add if they want a custom client, and a name for the custom client:

For example:

scopes:
     graph1l/schema/graph_1.schema
          client: url<to>/Graph1Client
     graph2l/schema/graph_2.schema
          client: url<to>/Graph2Client
          
This way, when we generate the files, it generates it and attaches it to the client. If none is specified, it automatically just attaches it to GraphQLClient by default.

As for their client, they should make it themselves. (as us generating it for them wouldn't make sense, as there is way too much customizability and functionality we can't account for).