Fixes #49623

This makes the TLS configuration resolution a bit more reasonable and predictable.

The main fix is that when a GraphQL client declares a specific TLS configuration, it will be used (currently it uses the default one instead of the named one if the default one has some trust options defined, which is clearly a bug).

As a side fix, when the deprecated properties (`quarkus.smallrye-graphql-client.CLIENT-NAME.key-store` and `quarkus.smallrye-graphql-client.CLIENT-NAME.trust-store`) are defined, they will now always take precedence over TLS configuration (logging a warning if an explicit TLS config is supplied too). Before this PR, they would or would not take precedence depending on whether the default TLS configuration had trust options defined or not, which is very weird.

I'm planning to remove the deprecated properties soon anyway, but I wanted to split it into steps so that this step can be backported to 3.20.