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?

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 proactively spot issues and guarantee that we pass the Kubernetes Storage conformance tests.

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 upstream e2e tests run against 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?

Local + 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

[github-actions]

Code Coverage Diff

This PR does not change the code coverage

[AndrewSirenko]

/retest

/ok-to-test

/test pull-aws-ebs-csi-driver-e2e-single-az

[AndrewSirenko]

/test pull-aws-ebs-csi-driver-e2e-single-az

[AndrewSirenko]

/retest

Seems like e2e flake, NOT cluster up flake:

  [FAIL] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy [It] (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents

[ConnorJC3]

/lgtm

[torredil]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: torredil

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 [torredil]

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

[AndrewSirenko]

/retest

Windows e2e flake unrelated to kops

Kubernetes e2e suite: [It] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works expand_more
--

I've seen this flake a few times in the past two weeks. making backlog item to look into it.