Visibility API: propagate manager kubeConfig to visibility API server

[tenzen-y]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The current visibility server generates and uses the visibility server dedicated KubeConfig, which does not have client configurations specified in Config API:

kueue/apis/config/v1beta1/configuration_types.go

Line 381 in 9ac669d

type ClientConnection struct {

After this PR, the manager root KubeConfig are propagated to visibility server and it uses the same KubeConfig as the manager.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Visibility API: Fix a bug that the Config clientConnection is not respected in the visibility server.

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	f09bab9
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/68e8edea74f4560008cf888f
😎 Deploy Preview	https://deploy-preview-7223--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mimowo]

Thank you 👍
/lgtm
/approve
/cherrypick release-0.14
/cherrypick release-0.13

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 696ed2ee8c1a0f3525aa414958305091f7b0cd50

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mimowo, tenzen-y

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mimowo,tenzen-y]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tenzen-y]

/cherrypick release-0.14
/cherrypick release-0.13

[k8s-infra-cherrypick-robot]

@tenzen-y: #7223 failed to apply on top of branch "release-0.13":

Applying: Visibility API: propagate manager kubeConfig to visibility API server
Using index info to reconstruct a base tree...
M	cmd/kueue/main.go
M	pkg/visibility/server.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/visibility/server.go
CONFLICT (content): Merge conflict in pkg/visibility/server.go
Auto-merging cmd/kueue/main.go
CONFLICT (content): Merge conflict in cmd/kueue/main.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Visibility API: propagate manager kubeConfig to visibility API server

In response to this:

/cherrypick release-0.14
/cherrypick release-0.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tenzen-y]

/cherrypick release-0.14

[k8s-infra-cherrypick-robot]

@tenzen-y: new pull request created: #7225

In response to this:

/cherrypick release-0.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.