Deprecate blueprint commands

[dantedallag]

Commit to start deprecation process of the az blueprint commands.

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

Related command

az blueprint

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

⚠️blueprint

rule	cmd_name	rule_message	suggest_message
⚠️ 1013 - SubgroupPropAdd	blueprint	sub group blueprint added property deprecate_info_target

[azure-client-tools-bot-prd]

Hi @dantedallag,
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]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[kairu-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kairu-ms]

Please fix the ci issues. BTW, it deserve a new extension version for release to public

[dantedallag]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 8419 in repo Azure/azure-cli-extensions

[dantedallag]

@kairu-ms I made the requested changes from the comments, except for the test case failures in CI. Our team owns blueprints, but we did not author these commands. I don't think I have the proper context to fix these test case errors and am also unsure why test cases are breaking if I did not make any functional changes?

Could you help out here?

[dantedallag]

@kairu-ms Could you provide assistance?