Quantum: Add --provider-id to 'az quantum target list' for provider-…

[v-elegacheva]

🤖 PR Validation — ⚠️ Review suggested

Breaking Changes
⚠️ None

⚠️Azure CLI Extensions Breaking Change Test

⚠️quantum

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	quantum target list	cmd quantum target list added parameter location
⚠️ 1006 - ParaAdd	quantum target list	cmd quantum target list added parameter provider_id
⚠️ 1009 - ParaPropRemove	quantum target list	cmd quantum target list update parameter resource_group_name: removed property required=True
⚠️ 1009 - ParaPropRemove	quantum target list	cmd quantum target list update parameter workspace_name: removed property required=True

…account target listing

---

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 azdev 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-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[microsoft-github-policy-service]

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

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).