[backport v2.10.1] AKS: Unable to upgrade Nodepool's k8s version

[github-actions]

This is a forwardport issue for #12860, automatically created via GitHub Actions workflow initiated by @richard-cox

Original issue body:

Setup
Rancher: v2.9-eaafb03a1ed78475258b7523b514168a8d9c8367-head
Dashboard: release-2.9 c2c221a

Describe the bug
Unable to upgrade Nodepool kubernetes version. "A new cluster version has been selected. Once the upgrade has completed, you can come back and upgrade the node pool version" warning is not getting cleared.

To Reproduce

• Provision AKS cluster from Rancher UI
• Upgrade control plane version to new one, valid warning is displayed for Nodepool
• Once the upgrade is finished, edit cluster and try upgrading Nodepool

Screenshots

2.9-head:

2.9.3 (as expected):

[izaac]

Reproduced in Rancher version 2.10.0

[izaac]

Rancher version: v2.10-c4944b3ca0b39c474121df9e7ef31f7aff4e4f7a-head
Dashboard UI version: release-2.10 624ad86

I used an AKS hosted cluster with multiple node pools.
Selecting a newer k8s version shows the info box as expected regarding the pools update option after update.
If I select the current version back, the info box is hidden as expected.

I did two version bumps:

• Update Kubernetes version. Save
• Wait until the checkbox is visible in the Edit view.
• Checked that multiple nodepools have this checkbox visible.
• Update Pool A and save. Wait for update.
• Go to edit again after waiting for the upgrade, Pool A is upgraded to the current kubernetes version. The checkbox is hidden.
• Navigating to Pool B which is still not upgraded has the upgrade checkbox visible and information about the upgrade to version.
• Check the box save and wait for Pool B to be upgraded.
• All the pools match the kubernetes versions after the upgrade and going to edit.
• Previous versions before the current in the Kubernetes versions dropdown are hidden

---

• Next Scenario, version bump, repeat the above.

CLosing as validated.

[zh-zywave]

This should be re-opened in my opinion, I don't think this was fully fixed in 2.10.1. For me, the button is still greyed-out when I want to make any changes to the cluster configuration for an imported cluster.

[richard-cox]

@zh-zywave can you create a new issue please and include as much detail as you can on how to reproduce and the environment (including the current and intended upgrade version of k8s)?