Revert "spring-cloud: add support to enable/disable MSI (#1523)"

[leonard520]

This reverts commit 666bab7.

---

This checklist is used to make sure that common guidelines for a pull request are followed.

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?

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 PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

[yonzhan]

add to S169

[qwordy]

Is there any reason?

[leonard520]

Is there any reason?

We have another spring cloud feature whose backend is ready and want to deliver soon.
#1419
In the meanwhile, our feature backend will be ready in another 3 weeks.
That's why I need to revert the CLI part for ours so that my teammate can release theirs in time.
Sorry fro the inconvenience brought.

[yungezz]

Is there any reason?

We have another spring cloud feature whose backend is ready and want to deliver soon.
#1419
In the meanwhile, our feature backend will be ready in another 3 weeks.
That's why I need to revert the CLI part for ours so that my teammate can release theirs in time.
Sorry fro the inconvenience brought.

HI @leonard520 in future if you have features under development, not ready to release, you can still work on your Azure CLI PR at same time, just label Azure CLI PR with do-not-merge, we'll review it but not merge it.