{CI} Add new comment to explain the reason that pin the wheel to 0.30.0

[wangzelin007]

---

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?

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

[bebound]

azure-cli released the version pin in Azure/azure-cli#12782.
We can port this to azure-cli-extension.

[wangzelin007]

WHEEL_INFO_RE just gets package-related information through a regular expression
If we replace it with pkginfo, then all packages must be downloaded before they can be parsed, otherwise ValueError will be raised.
At the same time, the parsed content is also different from the WHEEL_INFO_RE.
The essence of this test is to check whether the package name meets expectations.
Maybe we should transplant the WHEEL_INFO_RE code directly and remove the dependence on the wheel package.
Actually I have found the code for WHEEL_INFO_RE in scripts/ci/util.py.

WHEEL_INFO_RE = re.compile(
    r"""^(?P<namever>(?P<name>.+?)(-(?P<ver>\d.+?))?)
    ((-(?P<build>\d.*?))?-(?P<pyver>.+?)-(?P<abi>.+?)-(?P<plat>.+?)
    \.whl|\.dist-info)$""",
    re.VERBOSE).match

[wangzelin007]

Since wheel > 0.30.0 will not generate the metadata.json file, if we upgrade the wheel version, it may affect the installation, upgrade, and release of all extensions, so sufficient testing is required before upgrading the wheel.