fix: ignore the case when updating tags

[nilo19]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The tags on azure are case-insensitive for both keys and values. We need to ignore the case when comparing existing and new tags.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

fix: ignore the case when updating Azure tags

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

/triage accepted
/sig cloud-provider
/area provider/azure
/priority critical-urgent
cc @feiskyer

[nilo19]

/retest

[feiskyer]

/lgtm

[nilo19]

/assign @cheftako

[cheftako]

/lgtm
Can we specify in the release notes that this is an Azure user facing change?

[nilo19]

@cheftako could you please take a look again?

[cheftako]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cheftako, feiskyer, nilo19

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:

• staging/src/k8s.io/legacy-cloud-providers/OWNERS [cheftako]

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

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[ialidzhikov]

@nilo19 , I see you created backports for 1.20 and 1.21 but backport for 1.22 is missing? Can you please check?

[nilo19]

@ialidzhikov yeah, I need #104705 to be merged and I will continue the cherry pick.

[saschagrunert]

@nilo19 please open all cherry-pick PR's in parallel if possible, that way we can ensure that they merge (almost) simultaneously.