Replace email address for test recording files

[evelyn-ys]

Secrets have been handled in #8358
So this PR is for email addresses only

---

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

❌firmwareanalysis

rule	cmd_name	rule_message	suggest_message
❌ 1010 - ParaPropUpdate	firmwareanalysis firmware create	cmd firmwareanalysis firmware create update parameter firmware_id: updated property aaz_default from f586dbee-5156-4e29-9b0e-dee8eebc073a to a0675be7-2f1e-4692-95b2-5b681c52b41f	please change property aaz_default from a0675be7-2f1e-4692-95b2-5b681c52b41f to f586dbee-5156-4e29-9b0e-dee8eebc073a for parameter firmware_id of cmd firmwareanalysis firmware create
❌ 1010 - ParaPropUpdate	firmwareanalysis firmware create	cmd firmwareanalysis firmware create update parameter firmware_id: updated property default from f586dbee-5156-4e29-9b0e-dee8eebc073a to a0675be7-2f1e-4692-95b2-5b681c52b41f	please change property default from a0675be7-2f1e-4692-95b2-5b681c52b41f to f586dbee-5156-4e29-9b0e-dee8eebc073a for parameter firmware_id of cmd firmwareanalysis firmware create

[azure-client-tools-bot-prd]

Hi @evelyn-ys,
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]

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

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey