Creating CLI extension for Azure Quantum

[anpaz]

---

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

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 PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

[azuresdkci]

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:

docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/anpaz-msft/azure-cli-extensions.git@master#subdirectory=src/$EXT&egg=$EXT"

[qwordy]

Please use same tense in help.

az quantum -h

Group
    az quantum : Manage Azure Quantum Workspaces and submit jobs to Azure Quantum Providers.
        This command group is in preview. It may be changed/removed in a future release.
Subgroups:
    job       : Manage jobs for Azure Quantum.
    target    : Manage execution targets for Azure Quantum workspaces.
    workspace : Manage Azure Quantum workspaces.

Commands:
    execute   : Submits a job for quantum execution on Azure Quantum, and waits for the result.

[qwordy]

Are you still working on this PR?

[yungezz]

hi @anpaz-msft are you still on this PR? If yes, could you pls look at comments and fix CI failure? Feel free to ping us if any question.

[yungezz]

ping @anpaz-msft again for update

[anpaz]

Based on feedback I received offline, I was requested to hold this until Azure Quantum service in in public preview; currently we are on Private Preview.

[qwordy]

@anpaz @ricardo-espinoza Thank you for your work on this PR! It is really a large PR. I will merge it now. I created a issue #2956. We can discuss and resolve them in later releases.

[ReaNAiveD]

Usually, we output warnings to stderr. Is there any reason to allow them to be sent to stdout?