Add TL toggle on vm repair create to allow nested virtualization on repair VMs

[Sandido]

---

Trusted Launch does not currently allow Nested Virtualization connection. This is useful for our customer support engineers so we want to ensure they can continue this practice when needed.
This PR adds a toggle to turn off Trusted Launch in the repair VM. This will only occur when the user provides a decryption key for the vm.
In the standard case, the repair VM will not be Trusted Launch by default.

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

⚠️vm-repair

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	vm repair create	cmd vm repair create added parameter disable_trusted_launch

[azure-client-tools-bot-prd]

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

Hi @Sandido

Release Suggestions

Module: vm-repair

• Update VERSION to 1.2.0 in src/vm-repair/setup.py

Notes

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

[yonzhan]

Please fix CI issues

[Sandido]

Please fix CI issues

The error is in the Extension Index calculation:
"
AssertionError: {'aze[979 chars]zure-identity (==1.17.1)', 'azure-identity==1.[910 chars]0.0'} != {'aze[979 chars]zure-mgmt-resource (<23.0.0,>=3.0.0)', 'azure-[855 chars]0.0'}
2024-09-20T16:10:38.7730738Z Diff is 3752 characters long. Set self.maxDiff to None to see it. : Metadata for ml-2.30.0-py3-none-any.whl in index doesn't match the expected of:
"

Seems unrelated to my changes. @yonzhan , is there a setting in the CI check for maxDiff that needs to be set?

[zhoxing-ms]

@yanzhudd Could you please help take a look at this issue?