[AVM Module Issue]: Update remaining modules' Private Endpoints schema once they pass in main

[krbar]

Check for previous/existing GitHub issues

• [X] I have checked for previous/existing GitHub issues

Description

Diverse modules currently fail in main (e.g., due to WAF-reliablity) and can hence not be updated with to lastest Private Endpoints schema as they'd just fail in main again without publishing the update.

This issue is intended to track these modules to enable a future update as they are fixed.

cc: @AlexanderSehr

### Tasks
- [ ] update PE schema in `avm/res/cognitive-services/account`
- [ ] update PE schema in `avm/res/container-registry/registry` (#3215)
- [ ] update PE schema in `avm/res/desktop-virtualization/host-pool` (#3170)
- [ ] update PE schema in `avm/res/digital-twins/digital-twins-instance`
- [x] update PE schema in `avm/res/storage/storage-account` (not failing in main, but the PR #2997 was already open before started the bulk updates)

[microsoft-github-policy-service[bot]]

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!TIP] For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.