Quanum: Don't use endpoint cache when workspace doesn't match

[Pavel Braginskiy (pavelbraginskiy)]

Currently setting a default quantum workspace caches the workspace's endpoint, but then that endpoint is still used for all other workspaces, preventing them from being accessed.

This PR saves the workspace information together with the endpoint so that the cached endpoint value is not used for any other workspace.

---

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

Related command

az quantum workspace set

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

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]

Hi Pavel Braginskiy (@pavelbraginskiy),
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 pyproject.toml (or setup.py, if the extension has not migrated yet) as well.

[azure-pipelines]

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

[Yong Zhang (yonzhan)]

quantum

[Zulfat Nutfullin (rigidit)]

add Quantum prefix to PR title