Add vms pool implementation in 1.27

[wenxuan0923]

What type of PR is this?

/kind feature

Optionally add one or more of the following kinds if applicable:

-->

What this PR does / why we need it:

Add implementation to support VMs pool autoscaling. It does not support GPU pool for now (will be handled later).
It is same with #6951, but for version 1.27

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

1. Add a new toggle EnableVMsAgentPool to guard the behavior for VMs pool - it is default to false (azure_config.go)
2. Send List AP request to AKS-RP for constructing cache for vms pool - this will make sure it works for VMs pool with 0 node. (azure_cache.go)
3. Add a generic NodeTemplate which supports both VMSS and VMs agentpool, it will be used for scaling up VMs pool with 0 node. Before this change, only VMSS instance can be used as node template. (azure_template.go)
4. Add implementation for VMs pool, it supports scaling up by sending PUT AP request to AKS, and scaling down through DELETE machines request. It will use Deallocate mode from the agentpool to decide whether to delete or deallocate vm. (azure_vms_pool.go)

Does this PR introduce a user-facing change?

NONE (change is guarded by a toggle enableVMsAgentPool which is default to false. No cx-facing change right now.)

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

[k8s-ci-robot]

Hi @wenxuan0923. 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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wenxuan0923
Once this PR has been reviewed and has the lgtm label, please assign x13n for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• cluster-autoscaler/OWNERS

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

[comtalyst]

Overall looking good, left some comments

[comtalyst]

I would recommend adding some notes here regarding the current nature of this feature (e.g., for testing only, not production ready)

[comtalyst]

Is the difference between this and Taints just the data type and usage?
Wondering if there is a way to make that more intuitive, maybe adding a comment?

[comtalyst]

/ok-to-test