Quarkus Kubernetes client bean is always injected into the Kubernetes component

### Bug description

The `quarkus-kubernetes-client` extension produces a `KubernetesClient` which will always get autowired into the Camel component.

The downside of this is that none of the Camel component or endpoint options will have any effect by default, unless autowiring is disabled.

Potentially this is confusing UX as folks may not know that the Quarkus extension configuration is taking precedence over Camel. It also means that the Quarkus `KubernetesClient` bean is also likely automatically used by other extensions like `master` & `kubernetes-cluster-service`.

Start by tracing how the quarkus-kubernetes-client extension produces a KubernetesClient and how the Camel Kubernetes component autowires it. Review the component and endpoint options alongside the interactions with master and kubernetes-cluster-service. Done means the intended precedence is defined and verified so component or endpoint options are not unexpectedly overridden by default.

Written by the indexing model from the issue text.