Remove 'provided' scope from some client dependencies

[jmartisk]

Kinda a continuation of #2196
The idea is that a standalone Java SE app should only need to declare the smallrye-graphql-client-implementation-vertx dependency and be able to fully run with just that. This fixes the usage of dynamic client this way

[t1]

I can understand the intention, but then we have to exclude these dependencies when the client runs, e.g., within an application runtime that already brings these dependencies OOTB.

Maybe we should add a module smallrye-graphql-client-standalone or something?

[jmartisk]

I can understand the intention, but then we have to exclude these dependencies when the client runs, e.g., within an application runtime that already brings these dependencies OOTB.

Please elaborate on which case you're talking about - for example, when developing for WildFly and a WAR packaging, you would declare just a provided dependency on smallrye-graphql-client-api, so you don't get any of this included in the WAR.. (and even if you depend on the whole smallrye-graphql-client-implementation-vertx, then as long as it's provided, it doesn't get into the WAR)

With Quarkus, these are already added by Quarkus anyway, and it wouldn't work without them.

[jmartisk]

With WF feature pack 2.5.0, you should just be able to just compile with a provided dependency and you need exactly nothing else, not even declare a META-INF/MANIFEST.MF dependency on any wildfly modules, the modules should be added automatically, based on detecting a @GraphQLClientApi annotation in the deployment (we might need to figure out how to do it for dynamic clients too)

[t1]

You're right. Sometimes I'm astonishingly stupid 😳 Sorry.