fix: update Azure Managed Tag Logic

[charliedmcb]

What type of PR is this?

/kind bug

What this PR does / why we need it:

While working on the labels code, I noticed that we just directly port vmss tags into the expected node labels. However, for azure they don't have the same form in all cases. For AKS managed labels in particular, they typically have a different prefix. This prefix is something that we can translate the keys for the managed tags, and labels.

While I don't think this change is critical, as I doubt many users would be trying to have selectors on these labels, its still a bug/incorrect assumption within the current logic.
 

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Not highest priority, but something that should technically be fixed.

Does this PR introduce a user-facing change?

- Azure: fixing some logic within the synthesizing of expected node managed labels for the scale up from 0 case.

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

[k8s-ci-robot]

Hi @charliedmcb. 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: charliedmcb
Once this PR has been reviewed and has the lgtm label, please assign comtalyst 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/cloudprovider/azure/OWNERS

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