{CI} Add build wheel check and extension name check

[wangzelin007]

---

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

Related command

The name in setup.py should be the same as the extension dir name.
Otherwise the test case test_index will report an error:

At the same time, we should restrict setup.py to not allow the use of underscores, otherwise the version information of the build package cannot be obtained after user install the extension.

Only if the name contains an underscore, the version information cannot be displayed. This problem only appeared recently, and only packages built on the ci environment have problems, which cannot be reproduced in the local environment. The root cause has not yet been found.

Add build wheel check and extension name check to avoid the same error:

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)

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