Bump kubernetes version and use Giantswarm image repo

[bdehri]

What this PR does / why we need it

In order to update kubernetes, we need to change imageRepository as coredns image path is not calculated correctly.

• CI failure: capi-e2e-release-1-1-1-23-1-24 is failing consistently  kubernetes-sigs/cluster-api#7768
• KCP >= v1.2.8 and >= v1.3.0 doesn't work with certain Kubernetes versions kubernetes-sigs/cluster-api#7833

Checklist

• Update changelog in CHANGELOG.md.

Trigger e2e tests

/test create
/test upgrade

[tityosbot]

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

[bdehri]

/test all

[tityosbot]

@bdehri: No jobs can be run with /test all.
The following commands are available to trigger jobs:

• /test create
• /test upgrade

In response to this:

/test all

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.

[bdehri]

/test create
/test upgrade

[bdehri]

Should we do anything about these values?
https://github.com/giantswarm/cluster-gcp/blob/main/helm/cluster-gcp/values.yaml#L56

  etcd:
    imageRepository: "docker.io/giantswarm"
    imageTag: 3.5.4-0-k8s

[bdehri]

As per our discussion, For etcd, We decided to remove image repository and keep image tag.

[bdehri]

/retest

[fiunchinho]

I think retest does not work

/test create
/test upgrade