azure: use correct capz release branches for cloud-provider-azure tests

[jackfrancis]

This PR modifies the cloud-provider-azure test jobs in two ways:

1. Periodic release jobs now run against the capz "latest release" branch (instead of main). This is to get regular signal before a cloud-provider-azure release that there is something unhealthy in the cloud-provider-azure<-->capz dependency at the intersection that will block the next cloud-provider-azure release. By fixing these issues before a release, we will do a better job of preventing blocking release issues.
2. Adds a new set of cloud-provider-azure tests that use the "latest" capz release (the same release branch that the cloud-provider-azure release tests depend upon). The purpose of these jobs is to anticipate breakage in cloud-provider-azure + capz before the commits are cherry-picked into the cloud-provider-azure release branches. As above, this will give more advance signal of issues, and will help to keep cloud-provider-azure release branch commit histories cleaner.

[jsturtevant]

If possible, these changes should be incorporated into https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-cloud-provider/azure/generate.sh

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chewong, jackfrancis

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:

• config/jobs/kubernetes/sig-cloud-provider/azure/OWNERS [chewong]

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

[k8s-ci-robot]

@jackfrancis: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key release-1.20.yaml using file config/jobs/kubernetes/sig-cloud-provider/azure/release-1.20.yaml
• key release-1.21.yaml using file config/jobs/kubernetes/sig-cloud-provider/azure/release-1.21.yaml
• key release-1.22.yaml using file config/jobs/kubernetes/sig-cloud-provider/azure/release-1.22.yaml
• key release-1.23.yaml using file config/jobs/kubernetes/sig-cloud-provider/azure/release-1.23.yaml
• key release-master.yaml using file config/jobs/kubernetes/sig-cloud-provider/azure/release-master.yaml

In response to this:

This PR modifies the cloud-provider-azure test jobs in two ways:

1. Periodic release jobs now run against the capz "latest release" branch (instead of main). This is to get regular signal before a cloud-provider-azure release that there is something unhealthy in the cloud-provider-azure<-->capz dependency at the intersection that will block the next cloud-provider-azure release. By fixing these issues before a release, we will do a better job of preventing blocking release issues.
2. Adds a new set of cloud-provider-azure tests that use the "latest" capz release (the same release branch that the cloud-provider-azure release tests depend upon). The purpose of these jobs is to anticipate breakage in cloud-provider-azure + capz before the commits are cherry-picked into the cloud-provider-azure release branches. As above, this will give more advance signal of issues, and will help to keep cloud-provider-azure release branch commit histories cleaner.

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.