Merge dev into #33928 and resolve conflicts in managed_cluster_decorator.py

[Copilot]

Related command

az aks update

Description

PR #33928 (--enable-hosted-system, --system-node-subnet-id, --node-subnet-id on az aks update) went dirty against dev. This merges the current dev into the PR branch and resolves the conflict.

• Single conflicting file: src/azure-cli/azure/cli/command_modules/acs/managed_cluster_decorator.py. dev added update_upstream_kubescheduler_user_configuration at the same insertion point where the PR added update_hosted_system_profile, producing overlapping hunks for both the method bodies and their call sites in update_mc_profile_default.
• Both sides kept verbatim — no behavioral edits to either feature. Ordering in update_mc_profile_default: kube-scheduler config, then hosted system profile.
• Remaining files (_help.py, _params.py, custom.py, linter_exclusions.yml, tests) auto-merged.

Note: the merge commit lands on this branch rather than reneeli123:reneel/hobo-migration, which is not writable from here; it needs to be pulled into the fork branch to clear the conflict on #33928.

Testing Guide

azdev test acs --tests test_managed_cluster_decorator

History Notes

No customer-facing change; merge conflict resolution only. History note remains that of #33928.

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[azure-client-tools-bot-prd]

Hi Copilot,
Since the current milestone time is less than 7 days, this pr may not catch up with this release.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.