Jenkins pipeline can authenticate to both manager and managed (or to-be-managed) cluster and pass kubeconfig/credentials into the test run. When the managed cluster is not yet bound, the job uses the to-be-managed cluster kubeconfig so setup can add it to the manager (fleet management is setup-only; tests focus on Fleet Virtualization).

As a CI/CD maintainer, I want the Jenkins job to support dual-cluster auth and to find/read kubeconfig for both clusters (with fallback to to-be-managed when managed is not bound), so that Fleet Virtualization test runs have the correct credentials and kubeconfig available and setup can perform fleet management if needed.