{CI} Fix azure iot ops 2.0.1 index

[wangzelin007]

---

Introduced by PR: #9356
Maybe we need add checks for index schema.

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]

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

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

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

[Copilot]

Pull Request Overview

This PR restructures metadata for the azure-iot-ops package to follow Python packaging best practices. The changes separate contact information into distinct fields and reorganize project URLs into the appropriate nested structure.

Key Changes:

• Separated email and name in contact information from a combined format
• Moved project URL from root-level project_url to nested python.details.project_urls structure
• Removed description_content_type field from metadata

[bebound]

This is from the new format. We should make the script compatible with new format instead of manually changing it to old format.

https://github.com/Azure/azure-iot-ops-cli-extension/blob/c8a124bfcaddfc3926013c7c3b259e28ebc31f6a/pyproject.toml#L41-L42

Ref: https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#urls

[bebound]

Approved as a temp fix.
We need to update the related code later.