[AKS] support --yes for az aks mesh upgrade commands.

[deveshdama]

---

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

Related command

az aks mesh upgrade rollback -g myResourceGroup -n myCluster --revision asm-1-20
az aks mesh upgrade complete -g myResourceGroup -n myCluster

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️aks-preview

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	aks mesh upgrade complete	cmd aks mesh upgrade complete added parameter yes
⚠️ 1006 - ParaAdd	aks mesh upgrade rollback	cmd aks mesh upgrade rollback added parameter yes

[azure-client-tools-bot-prd]

Hi @deveshdama,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

AKS

[github-actions]

⚠️ Release Suggestions

Module: aks-preview

• Update version to 3.0.0b7 in setup.py

Notes

• Stable/preview tag is inherited from last release. If needed, please add stable/preview label to modify it.
• Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add major/minor/patch/pre label to adjust it.
• For more info about extension versioning, please refer to Extension version schema

[FumingZhang]

lgtm

But I find there's no scenario test for command aks mesh upgrade rollback/complete, a passed live test could help ensure that everything is working properly.

[FumingZhang]

Live test passed

• test_aks_azure_service_mesh_canary_upgrade

[FumingZhang]

CI failure is not related to the change in this PR, would be fixed in #7548.

>               self.agentpool.windows_profile.disable_windows_outbound_nat is not None
            ):
E           AttributeError: 'AgentPoolWindowsProfile' object has no attribute 'disable_windows_outbound_nat'

[yanzhudd]

/azp run

[azure-pipelines]

Pull request contains merge conflicts.

[yanzhudd]

Please resolve the code conflict.

[deveshdama]

resolved.

[azclibot]

[Release] Update index.json for extension [ aks-preview ] : https://dev.azure.com/azclitools/release/_build/results?buildId=152072&view=results