Bump K8s libs to 0.25.3

[lobziik]

/kind bug
/kind cleanup

What this PR does / why we need it:
Bug described in kubernetes/kubernetes#112793 was introduced in released versions of k8s.io/cloud-provider, namely in v0.25.(0, 1, 2). This was fixed in the most recent k8s.io/cloud-provider version v0.25.3. This PR bumps k8s libs to bring this fix into cloud-provider-aws.

Also, this patch bumps k8s libs version for the e2e test suite.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

@lobziik: This issue is currently awaiting triage.

If cloud-provider-aws contributors determine 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]

Hi @lobziik. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[dims]

/ok-to-test

[olemarkus]

/retest

[olemarkus]

Doesn't look like the version bumps pass tests just like that, unfortunately. It errors out in a panic.

[olemarkus]

/cc @nckturner

[lobziik]

@olemarkus I rolled back bump for e2e suite, k8s.io/kubernetes/test/e2e/framework introduces dependency on ginkgo v2 which caused this panic as far as i understand.

I suggest to address dependency bump for e2e suite in follow-up PR, this shouldn't affect this test essence i think.

[olemarkus]

I thought we already bumped to ginkgo v2. I've seen this error before when one used mixed versions though. We'll have a look in a followup PR.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: olemarkus

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

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