[ARM] Migrate resource to track2 SDK

[zhoxing-ms]

Description

This PR upgrades the Python SDK version of azure-mgmt-resource from 12.1.0 to 16.1.0

Here are the main changes for resource migration to track2:

1. LRO operations are renamed to begin_xxx_xxx. For example in track1, the name is create_or_update; while in track2, the name is begin_create_or_update.
2. When api-version is less than 2019-10-01, the parameters of all deployment operations are changed from DeploymentProperties to Deployment, which is consistent with the SDK after version 2019-10-01.
3. The objects of input parameters for some methods are further encapsulated:

• begin_what_if(): DeploymentWhatIfProperties --> DeploymentWhatIf
• begin_what_if_at_subscription_scope()/...: DeploymentWhatIfProperties --> ScopedDeploymentWhatIf
• begin_export_template(): flattened parameters --> ExportTemplateRequest
• begin_move_resources(): flattened parameters --> ResourcesMoveInfo
• links_client.create_or_update(): ResourceLinkProperties --> ResourceLink
• tags.create_or_update_at_scope(): flattened parameters --> TagsResource
• tags.update_at_scope(): flattened parameters --> TagsPatchResource

4. In method get() of ResourcesOperations, some parameters are passed in through **kwargs instead
5. CloudError and HttpOperationError are replaced by HttpResponseError
6. In track 2, the logic corresponding to the class name of Codegen generating operations changes, so DeploymentOperations becomes DeploymentOperationsOperations
   For more details, please refer to this issue: remove double "operations" in operation group names autorest.python#910 (comment)
7. config in management client becomes a private variable _config.
8. In method policy_definitions.create_or_update_at_management_group(), the positions of parameters management_groupand parameters are reversed.
9. generate_client_request_id in ResourceManagementClientConfiguration no longer needs, SDK automatically add x-ms-request-id now through the RequestIdPolicy
10. The accept_language is no longer supported in ResourceManagementClientConfiguration, so the fixed value en-US in track 2 is hard coded.
11. The pipeline and policy in management client migrated from msrest to azure-core. And when doing ARM deployment, the pipeline needs to add custom policy JsonCTemplatePolicy() to support JSON templates.
12. get_by_id() and get() of ResourcesOperations no longer support parameter raw, but passes in a callback method cls instead. So the custom callback function add_response_body() is used to realize the logic of include_response_body.
13. The resource action lacks generic POST operation in Swagger, so for the time being, AzureOperationPoller of msrestis still used for low-cost migration. And the request way is changed to pipeline.run in track 2.
14. Before version 2019-08-01, get_by_id() and get() of ResourcesOperations lacked parameter api-version. The problem was solved by modifying the Swagger to regenerate a new Python SDK. PR link: Swagger PR
15. Fix some live tests due to the changes in track2.

Known commands that are not covered by test

1. appservice domain create
2. appservice ase create

Migration for extension
PR link: Azure/azure-cli-extensions#3355

Live Test
result link

TODO

• Refactor the temporary code in the subsequent PR Refactor the temporary code in migration track 2 of resource module #18023

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

---

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.

[yonzhan]

ARM

[jiasli]

Consider using per_call_policies introduced by Azure/azure-sdk-for-python#17340.

It requires azure-core 1.13.0 which is bumped by #17671.

[jiasli]

_prepare_client_kwargs_track2 from core already configures x-ms-client-request-id.

azure-cli/src/azure-cli-core/azure/cli/core/commands/client_factory.py

Lines 156 to 158 in 039fa21

	# Prepare x-ms-client-request-id header, used by RequestIdPolicy
	if 'x-ms-client-request-id' in cli_ctx.data['headers']:
	client_kwargs['request_id'] = cli_ctx.data['headers']['x-ms-client-request-id']

[jiasli]

Migrate for extension

I would suggest we provide a method for users to revert back to old versions of Azure CLI because these are not small changes and may break extensions, especially those not in azure-cli-extensions (#13653).

[jiasli]

Please kindly put this PR on hold until #17671 and #17812 are merged so that they can be tested together.

Update: ✔ #17671 and #17812 are merged. Please merge from dev.

[kairu-ms]

Can we get the Deployment model from SDK which api-version less than 2019-10-01

[zhoxing-ms]

Yes, because in track 2, the SDK before version 2019-10-01 has added this model
Related code: code link

[kairu-ms]

Same concern as above.

[qwordy]

Approve vm part