AAD related changes in dataprotection aks ext CLI

[anshulahuja98]

---

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.

For Backup Team

Manual tests performed

• Install extension without specifying anything related to AAD-> verified populated useAAD true and SA Uri.
• Install extension with useAAD = true -> verified populated useAAD true and SA Uri.
• Install extension with useAAD = false -> verified populated useAAD false and SA Uri.
• Update existing extension with useAAD and URI empty -> URI gets populated.
• Update current extension with no new params -> URI populated.

[anshulahuja98]

Draft currently, will raise after internal review and as per our required release timelines.
Merge ETA >1month

[anshulahuja98]

Discussed pipeline test failures with Bavneet, the team is aware of this bug and working on it.
Test failures are unrelated to my code changes

[Miraj50]

Reviewed.

[anshulahuja98]

Final round of review and testing from Backup team is done
We require this PR To be merged around 15 January.

For certain pipeline test failures, had pinged, @bavneetsingh16 that those are known issues and not regressed due to this PR

extension team will take up fix in early january.

Please let us know if there is any risk in merging/ releasing this around 15 January.