[Spring] Private DNS zone support

[Descatles]

---

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[bot]]

⚠️Azure CLI Extensions Breaking Change Test

⚠️spring

rule	cmd_name	rule_message	suggest_message
⚠️ 1011 - SubgroupAdd	spring private-dns-zone	sub group spring private-dns-zone added

[azure-client-tools-bot-prd[bot]]

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

Spring

[github-actions[bot]]

:warning: Suggestions

Module: spring

• Update version to 1.21.0 in setup.py

Notes

• Stable/preview tag is inherited from last release. If needed, please add stable/preview label to modify it.
• Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add major/minor/patch/pre label to adjust it.
• For more info about extension versioning, please refer to Extension version schema