[dataprotection] Support for vaulted blob backups

[zubairabid]

---

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

Related command

• az dataprotection backup-instance initialize-backupconfig: Added parameters --vaulted-backup-containers to provide list of containers to backup
• az dataprotection backup-instance initialize-backupconfig: Added parameters --include-all-containers, --storage-account-name, storage-account-resource-group to backup all containers in a storage storage-account-resource-group
• az dataprotection backup-instance update: New command, which takes --vaulted-blob-container-list to which we pass the output of initialize-backupconfig
• az dataprotection backup-instance update-policy: Had a bug where policy update for a vaulted blob container would remove the backed up containers entirely. This was rewritten to fix that
• az dataprotection backup-instance restore initialize-for-item-recovery: now takes --vaulted-blob-prefix-pattern, a new prefix pattern for vaulted blobs restore

General Guidelines

• [x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• [x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• [x] 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.