Add K8s 1.31 to CI by pinning kops commit instead of version

[AndrewSirenko]

Is this a bug fix or adding new feature?
CI

What is this PR about? / Why do we need it?

/hold

This PR should not be merged until we fix any rate-limit issues in our CI (likely by submitting a PR to kops for different retry policies)

We want our CI to test changes to the EBS CSI Driver against the latest stable version of Kubernetes to pro-actively spot issues and guarantee that we pass the Kubernetes Storage conformance tests. Our pre-submit tests build an image of our driver, create a kops or EKS cluster, install the driver via Helm/Kustomize, and run the upstream kubernetes-e2e or our EBS-e2e test-suites.

However, EKS and recently kOps do not release support for the latest stable Kubernetes version until 1-2 months afterwards, which blocks us from upgrading our CI to the latest Kubernetes version.

Many of the upstream testgrid tests use kubetest2-kops to test newer versions of Kubernetes without the latest kops version (see test-infra jobs). This is because there are usually a few unreleased fixes on the main branch that allow kops to be used for newer Kubernetes versions when combined with exporting KOPS_RUN_TOO_NEW_VERSION=true. This PR pins our CI to a Kops commit instead of a release so that we can do the same with our custom cluster testing system.

What testing is done?

CI

[k8s-ci-robot]

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

[k8s-ci-robot]

[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 andrewsirenko. 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

[github-actions]

Code Coverage Diff

This PR does not change the code coverage

[k8s-ci-robot]

PR needs rebase.

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.