[release-1.30] Bump konnectivity-client to v0.30.2

[jkh52]

What type of PR is this?

/kind feature

What this PR does / why we need it:

• apiserver: no real changes to konnectivity-client
• konnectivity-server and konnectivity-agent:
  • use go 1.21 (Update go to 1.21 kubernetes-sigs/apiserver-network-proxy#550)
  • container images: default to non-root user (Use nonroot distroless image for agent and server kubernetes-sigs/apiserver-network-proxy#564)
  • see Full delta

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

This cherry pick PR is for a release branch and has not yet been approved by Release Managers.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved (/lgtm + /approve) by the relevant OWNERS.

If you didn't cherry-pick this change to all supported release branches, please leave a comment describing why other cherry-picks are not needed to speed up the review process.

If you're not sure is it required to cherry-pick this change to all supported release branches, please consult the cherry-pick guidelines document.

AFTER it has been approved by code owners, please leave the following comment on a line by itself, with no leading whitespace: /cc kubernetes/release-managers

(This command will request a cherry pick review from Release Managers and should work for all GitHub users, whether they are members of the Kubernetes GitHub organization or not.)

For details on the patch release process and schedule, see the Patch Releases page.

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/test-infra repository.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jkh52
Once this PR has been reviewed and has the lgtm label, please assign deads2k, dims, sttts for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS
• cluster/gce/OWNERS
• staging/src/k8s.io/apiextensions-apiserver/OWNERS
• staging/src/k8s.io/apiserver/OWNERS
• staging/src/k8s.io/cloud-provider/OWNERS
• staging/src/k8s.io/code-generator/OWNERS
• staging/src/k8s.io/controller-manager/OWNERS
• staging/src/k8s.io/dynamic-resource-allocation/OWNERS
• staging/src/k8s.io/kube-aggregator/OWNERS
• staging/src/k8s.io/kube-controller-manager/OWNERS
• staging/src/k8s.io/kubelet/OWNERS
• staging/src/k8s.io/legacy-cloud-providers/OWNERS
• staging/src/k8s.io/pod-security-admission/OWNERS
• staging/src/k8s.io/sample-apiserver/OWNERS
• vendor/OWNERS

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

[cici37]

/remove-sig api-machinery

[jkh52]

/assign @cheftako