[AKS] User is unable to remove original node pool

[timhaneunsoo]

Setup

• Rancher version: 2.6-head 68c6c13 but also reproducible in 2.6.3
• Browser type & version:

Describe the bug

After provisioning an AKS cluster, user is unable to remove original node pool while editing cluster. There is an option to add and remove a new node pool, but none to remove the original node pool.

This action is available when editing an EKS cluster on the original node pool

To Reproduce

1. Provision AKS cluster
2. After cluster becomes active, edit cluster
3. Navigate down to Node Pools section
4. Verify that user can add node pool, and the new node pool can be removed
5. Verify that user cannot remove original node pool, even after new node pool is added

Result User is not able to remove the original node pool.

Expected Result

User should be able to remove the original node pool, as they can in EKS

[mantis-toboggan-md]

This will be included in the work to port AKS provisioning from Ember to Vue: https://github.com/rancher/dashboard/issues/8965

One consequence of this change is that we need to add validation to ensure the user still has at least one pool with the system mode selected.

[nwmac]

@mantis-toboggan-md Zube has this in the 'To Test' column, but the label says Review - what's the status?

[mantis-toboggan-md]

@nwmac the correct status is 'To Test'