update k8s version to use 1.22.6 with the new images that is built

[cpanato]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

update the images we use in CI to the latest k8s releases, per this PR kubernetes-sigs/image-builder#795

and the new images are available to use

Displaying the generated image information
NAME                                      PROJECT                      FAMILY                      DEPRECATED  STATUS
cluster-api-ubuntu-1804-v1-20-15-nightly  k8s-staging-cluster-api-gcp  capi-ubuntu-1804-k8s-v1-20              READY
cluster-api-ubuntu-1804-v1-21-9-nightly   k8s-staging-cluster-api-gcp  capi-ubuntu-1804-k8s-v1-21              READY
cluster-api-ubuntu-1804-v1-22-6-nightly   k8s-staging-cluster-api-gcp  capi-ubuntu-1804-k8s-v1-22              READY
cluster-api-ubuntu-1804-v1-23-3-nightly   k8s-staging-cluster-api-gcp  capi-ubuntu-1804-k8s-v1-23              READY

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato

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

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

[cpanato]

/hold for non required tests but to make sure that is working

/assign @dims @sayantani11 @jayesh-srivastava

[cpanato]

/test ls

[k8s-ci-robot]

@cpanato: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-cluster-api-provider-gcp-build
• /test pull-cluster-api-provider-gcp-e2e-test
• /test pull-cluster-api-provider-gcp-make
• /test pull-cluster-api-provider-gcp-test
• /test pull-cluster-api-provider-gcp-verify

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-provider-gcp-capi-e2e
• /test pull-cluster-api-provider-gcp-conformance
• /test pull-cluster-api-provider-gcp-conformance-ci-artifacts

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-api-provider-gcp-build
• pull-cluster-api-provider-gcp-e2e-test
• pull-cluster-api-provider-gcp-make
• pull-cluster-api-provider-gcp-test
• pull-cluster-api-provider-gcp-verify

In response to this:

/test ls

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.

[cpanato]

/test pull-cluster-api-provider-gcp-capi-e2e
/test pull-cluster-api-provider-gcp-conformance

[cpanato]

/hold cancel

[sayantani11]

/lgtm