Adding managed identity subcommands and moving old identity commands to new subgroup

[jorge-beauregard]

---

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?

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]

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

[mayssamm]

The communication tests have not run (see under Checks, compare with a previous PR), I think because of the merge conflict that needs to be resolved first.

[mayssamm]

I don't think you have the latest in your main, latest is 1.6.0. Please sync your fork and update the PR. Also, for a change of this size, with all the auto generated code that runs behind the scenes updated, I would not recommend a minor version change. I would even recommend to bump the major version and going straight to 2 (2.0.0).

[lsundaralingam]

@jorge-beauregard, is this a breaking change?

[jorge-beauregard]

I checked that all previous functionality still worked exactly the same way as it used to. Aside from all generated code being revamped, the interaction the final user has is still the same