Quantum: fix quantum jobs test

[rigidit]

Fix test_submit in test_quantum_jobs that relied on returning jobs in wrong order

---

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 @rigidit,
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 fixes the test_submit test in test_quantum_jobs.py which was making incorrect assumptions about the default ordering of job listings. The test was expecting jobs to be returned in chronological order (oldest first), but the actual API behavior returns jobs in reverse chronological order (newest first).

Key Changes

• Updated assertions for --top 1 to expect the most recently submitted job (IonQ) instead of the oldest job (Rigetti)
• Updated assertions for --skip 1 to expect Rigetti jobs after skipping the most recent IonQ job
• Swapped the expected provider names in assertions to match the actual reverse chronological ordering

[kairu-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kikomiss]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 9481 in repo Azure/azure-cli-extensions

[kikomiss]

@kairu-ms this PR only touches existing tests and could be merged right away. No extension release needed.

[yonzhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).