Automate image dependency upgrades & Migrate to kubekins-e2e-v2

[AndrewSirenko]

Is this a bug fix or adding new feature? Automation

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

First, this PR automates two manual steps of our release process: updating the kubekins e2e image in our Helm chart, and updating the gcb-docker-gcloud image in our cloudbuild.yaml.

It combines these updates with our sidecar update script in the new Makefile target: update-image-dependencies

---

Second, kubekins-e2e is deprecated, so let's move to kubekins-e2e-v2

Quote from Kubernetes SIG-Testing slack:

• It is leaner than the old image. We got rid of many legacy CI deps/tooling that are specific to k/k and don't need to be used in most repos
• It is a multiarch image, amd64 and arm64. This is important as we'll be running arm64 nodes in Prow in the future and someone recently proposed dynamic scheduling in Prow so if it works out, we would benefit from having many cloud and architecture agnostic jobs.
• It is built directly from debian:bookworm instead of bootstrap(a sig-testing image built from debian with legacy CI deps).

Will update internal runbook after merge.

What testing is done?

./hack/release-scripts/update-e2e-images works! make update-image-dependencies works!

Lets hope CI is a fan of kubekins-e2e-v2...

[github-actions[bot]]

Code Coverage Diff

This PR does not change the code coverage

[AndrewSirenko]

/label tide/merge-method-squash

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ConnorJC3

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](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/OWNERS)~~ [ConnorJC3] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment