Fix Quantum e2e tests to obfuscate test recording data

[katymccl]

Obfuscate api keys, connection strings, subscription id, resource group name, resource name in recordings. This is in response to an MSRC flagged vulnerability

---

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 @katymccl,
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>

[Copilot]

Pull Request Overview

This PR adds comprehensive data obfuscation to the Quantum extension's end-to-end test recordings to prevent sensitive information from being checked into the repository. The changes enhance security by automatically redacting API keys, connection strings, subscription IDs, resource group names, and other sensitive quantum workspace data from test recording files.

Key Changes

• Added new PowerShell functions to obfuscate API keys and quantum workspace sensitive data
• Integrated the new obfuscation functions into the existing test recording cleanup process
• Extended the existing SAS token obfuscation with additional security measures

[github-actions]

Hi @katymccl

Release Suggestions

Module: quantum

• Please log updates into to src/quantum/HISTORY.rst
• Update VERSION to 1.0.0b7 in src/quantum/setup.py

Notes

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

[katymccl]

/azp run

[azure-pipelines]

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

[yonzhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[katymccl]

@yonzhan , @kairu-ms could you please help review and help me get this merged? this is just an update to our tests recordings in response to an information disclosure icm.

[kairu-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[katymccl]

@jsntcy can you please review this?

[katymccl]

I don't have permissions to merge this; @kairu-ms can you please merge this pr?