`az deployment sub create` returns unstructured error output message

[asilverman]

This is autogenerated. Please review and update as needed.

Describe the bug

The error output that the az tool is outputting is not structured and hard to read, see below:

➜  az deployment sub create -f main.bicep -l southcentralus
{"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"DeploymentFailed\",\r\n        \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.\",\r\n        \"details\": [\r\n          {\r\n            \"code\": \"Conflict\",\r\n            \"message\": \"{\\r\\n  \\\"error\\\": {\\r\\n    \\\"code\\\": \\\"VaultAlreadyExists\\\",\\r\\n    \\\"message\\\": \\\"The vault name 'fooBar' is already in use. Vault names are globaly unique so it is possible that the name is already taken. If you are sure that the vault name was not taken then it is possible that a vault with the same name was recently deleted but not purged after being placed in a recoverable state. If the vault is in a recoverable state then the vault will need to be purged before reusing the name. For more information on soft delete and purging a vault follow this link https://go.microsoft.com/fwlink/?linkid=2147740.\\\"\\r\\n  }\\r\\n}\"\r\n          }\r\n        ]\r\n      }\r\n    ]\r\n  }\r\n}"}]}}

Command Name
az deployment sub create

Errors:
The error message is hard to read and is shown to user in an unstructured way, please offer a better experience so that it is easier to use.

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• Ensure your deployment includes an acr with a name that already exists.
• az deployment sub create -f {} -l {}

Expected Behavior

A better structured error message

Environment Summary

Linux-5.10.16.3-microsoft-standard-WSL2-x86_64-with-glibc2.2.5
Python 3.8.11
Installer: HOMEBREW

azure-cli 2.27.0 *

Additional Context

[yonzhan]

ARM error handling

[anthony-c-martin]

Ariel Silverman (@asilverman) if possible, it would be helpful if you could also include the .bicep file you're using to deploy this resource.