feat: add workload-orchestration-preview extension

[atharvau]

Adds the preview extension for workload-orchestration with solution-deployment commands and advanced configuration management features.

• Solution deployment create/show/list/delete commands
• Multi-target deployment support
• Configuration optional and accepts string or JSON
• Custom location namespace changes
• Placeholder test (integration tests in stable extension)

---

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.

[Copilot]

Copilot wasn't able to review this pull request because it exceeds the maximum number of lines (20,000). Try reducing the number of changed lines and requesting a review from Copilot again.

[atharvau]

/azp run

[azure-client-tools-bot-prd]

Validation for Breaking Change Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Hi @atharvau,
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.

[azure-pipelines]

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

[yonzhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[atharvau]

Finish with Changes , we can move forward for review/merge

[necusjz]

@atharvau per https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md#cli-extension-version-transition-table, workload-orchestration itself already can support "preview functionality". why introducing an extra extension here?

[atharvau]

@atharvau per https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md#cli-extension-version-transition-table, workload-orchestration itself already can support "preview functionality". why introducing an extra extension here?

Hi @necusjz , we want to support and separate 2 different cli extension one Stable and one with preview . we have different customer use cases . we don't want upgrade our existing cli extension to preview version.

[necusjz]

@atharvau per https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md#cli-extension-version-transition-table, workload-orchestration itself already can support "preview functionality". why introducing an extra extension here?

Hi @necusjz , we want to support and separate 2 different cli extension one Stable and one with preview . we have different customer use cases . we don't want upgrade our existing cli extension to preview version.

that's fine. please add the new entry to Azure/aaz as well.

[necusjz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[atharvau]

@atharvau per https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md#cli-extension-version-transition-table, workload-orchestration itself already can support "preview functionality". why introducing an extra extension here?

Hi @necusjz , we want to support and separate 2 different cli extension one Stable and one with preview . we have different customer use cases . we don't want upgrade our existing cli extension to preview version.

that's fine. please add the new entry to Azure/aaz as well.

@necusjz we are not using aaz , we make custom code changes which are copilot based

[atharvau]

Everything look green @necusjz

[necusjz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[atharvau]

@necusjz @yonzhan /azp run

[yonzhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[atharvau]

Pipeline is green , thanks good to merge

[azclibot]

[Release] Update index.json for extension [ workload-orchestration-preview-0.1.0b1 ] : https://dev.azure.com/msazure/One/_build/results?buildId=168340317&view=results