[Feature] (Suggested) Sequencing of AKS "weekly" component updates in Fleet Manager

**Is your feature request related to a problem? Please describe.**

I want to ensure that updates are first deployed in the DEV environment before being applied to PROD.

**Describe the solution you'd like**

The same way that fleet manager can provide an ordering for update rollouts for Node OS and k8s Versions across environments, I'd like to be able to configure an ordering for the managed AKS component updates.

**Describe alternatives you've considered**

Deploying the DEV cluster in an alternative region that _should_ get the updates first. This seems hacky and there's no real guarantee here either. Furthermore it only scales to two stages, whereas we would actually want at least a three-environment configuration.

**Additional context**

I understand that planned maintenance for AKS control plane and cluster resource patches are best-effort and can be overridden for unplanned, critical operations. I have been informed by MS support that this is the reason why fleet manager doesn't provide sequencing for this. I would however like to at least be able to _suggest_ an order of operations that should be followed for _non-critical_ rollouts.

### References
- https://github.com/Azure/AKS/issues/2984
- https://github.com/Azure/AKS/issues/3156