{CI} Fix extension release pipeline: Migrate from storage sdk to azure cli commands.

[wangzelin007]

---

Since we have disabled the storage key, the extension release pipeline needs to be refacted to use the service principal + az command method instead of the storage key.

test screenshot:

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

Related command

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

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

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

CI

[jiasli]

Previously we adopted an approach in Azure CLI repo that during development and testing phase, scripts used in the release pipeline are put under a release-scripts branch, so that no PR is needed to update the scripts. Otherwise, each modification of a script would require a PR which is tedious. After scripts are fully tested, merge them to dev branch and switch to the ones on dev branch.