Overview/Summary

Deployment Name too long and Critical Updates Missing failure (V2.1.2)

This PR fixes/adds/changes/removes

c_AVD-HP-VM-MissingCriticalUpdates deployment would fail due to search syntax incorrectly defined
c_AVD-StorAcct-Over-100msLatencyClnt-Stor deployment name was still too long depencing on the name of the storage account appended
Additonal Alert names truncated to avoid deployment name length being over 64 characters (Trying to avoid logic to use GUIDs for clarity during deployment)
Removed Automation Account Diagnostics log retention which was deprecated (CARML)
Removed Alert - Missing Critical Updates as Table 'Update' is deprecated
Updated logic for host pool name to truncate if over 20 characters long only during deployment
VM Memory and CPU logic changed from checking every 1 min to every 5 min with thresholds based on 15 min vs 5 min average. (5/15 vs 1/5)
This was done to resolve false alerts during VM startup.

N/A

Redeployed in lab for both commercial and US Gov - successful

[X ] Read the Contribution Guide and ensured this PR is compliant with the guide
[X ] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
[X ] Checked for duplicate Pull Requests
[X ] Associated it with relevant GitHub Issues
[X ] (AVD LZA Team Only) Associated it with relevant ADO Items
[X ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ X] Performed testing and provided evidence.
[ X] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Docs etc.)