k8s-1.32: introduce k8s-1.32 kubevirtci provider

[brianmcarey]

What this PR does / why we need it:

The kubernetes v1.32.0 beta was released[1] - adding a new cluster provider for kubernetes v1.32

Manual run of:

bazel run //robots/cmd/kubevirtci-bumper -- \
        --ensure-latest=true \
        --force-target-major-minor '1.32' \
        --pre-release-version='beta.0' \
        --github-token-path='' \
        --k8s-provider-dir=$PROJECTS/kubevirtci/cluster-provision/k8s \
        --cluster-up-dir=$PROJECTS/kubevirtci/cluster-up

[1] https://github.com/kubernetes/kubernetes/releases/tag/v1.32.0-beta.0

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

/cc @dhiller @xpivarc

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from brianmcarey. 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

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

[kubevirt-bot]

@brianmcarey: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
check-provision-k8s-1.31	101012e	link	true	/test check-provision-k8s-1.31
check-provision-k8s-1.31-s390x	101012e	link	true	/test check-provision-k8s-1.31-s390x
check-provision-k8s-1.30-s390x	101012e	link	true	/test check-provision-k8s-1.30-s390x

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. I understand the commands that are listed here.