refactor: upstream most of Azure managed CAS changes in cloudprovider/azure for 1.28

[comtalyst]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

"Refactor" as a part of fork-upstream (managed-selfhosted) realignment. Should not have any breaking changes.
This codebases realignment will simplify the logistics between the two, cutting a significant portion of maintenance cost.

There will be a separate effort focusing on improve code quality, rather than realigning codebase.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

All are in cloudprovider/azure except go.mod, go.sum, and vendor.
Preferrably review 1.29 PR first, then compare it to here.
Unless specified, the differences are just linter changes and cloud-provider-azure version differences.

Overall:

• Bump cloud-provider-azure library to v1.28
  • The change of default VmType noted here is not applicable to us, because we have a forked layer of cloud-provider-azure, which already have the default of this field set to vmss
• Trivial code improvements (e.g., using constants for reused string literals, method interfaces, etc.)
• Support cloud provider AAD certificate authentication
• Add a new GPU label, with the old one being deprecated/switch out soon
• Temporarily adding new configuration options; primarily for managed offering, not being supported for self-hosted yet so don't rely on them until documented: EnableForceDelete (already in master), EnableDetailedCSEMessage, GetVmssSizeRefreshPeriod
• Add retry for creatingAzureManager in case of throttled requests (already in master)
• Add support for edge zones (already in master)

Does this PR introduce a user-facing change?

- Azure: update cloud-provider-azure library version to v1.28.0
- Azure: support cloud provider AAD certificate authentication
- Azure: add support for edge zones

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @comtalyst. 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-sigs/prow repository.

[comtalyst]

I believe the linter forces some of the logic to be moved to separate functions (e.g., getVMSSType)

[comtalyst]

In fact, I found several instances of potentially questionable implementations here. But the evaluation/refactor will be a separate effort.

[tallaxes]

/ok-to-test

[k8s-ci-robot]

@comtalyst: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-autoscaler-e2e-azure	7603a15	link	false	/test pull-cluster-autoscaler-e2e-azure

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

[tallaxes]

/lgtm
/approve

[feiskyer]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: comtalyst, feiskyer, tallaxes

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:

• cluster-autoscaler/OWNERS [feiskyer]

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