Out of date Azure RM backends

**Bicep version**
Latest Azure DevOps agent Bicep version as of 2022-07-28

**Describe the bug**
When deploying we are receiving this error sometimes:
```yaml
{
"status": "Failed",
"error": {
"code": "NoRegisteredProviderFound",
"message": "No registered resource provider found for location 'westeurope' and API version '2021-08-01' for type 'networkWatchers/flowLogs'. The supported api-versions are '2017-09-01, 2017-10-01, 2017-11-01, 2018-01-01, 2018-02-01, 2018-03-01, 2018-04-01, 2018-05-01, 2018-06-01, 2018-07-01, 2018-08-01, 2018-10-01, 2018-11-01, 2018-12-01, 2019-02-01, 2019-04-01, 2019-06-01, 2019-07-01, 2019-08-01, 2019-09-01, 2019-11-01, 2019-12-01, 2020-01-01, 2020-03-01, 2020-04-01, 2020-05-01, 2020-06-01, 2020-07-01, 2020-08-01, 2020-11-01, 2021-01-01, 2021-02-01, 2021-03-01'. The supported locations are 'westus, eastus, northeurope, westeurope, eastasia, southeastasia, northcentralus, southcentralus, centralus, eastus2, japaneast, japanwest, brazilsouth, australiaeast, australiasoutheast, centralindia, southindia, westindia, canadacentral, canadaeast, westcentralus, westus2, ukwest, uksouth, koreacentral, koreasouth, francecentral, australiacentral, southafricanorth, uaenorth, switzerlandnorth, germanywestcentral, norwayeast'."
}
}
```

It appears a few backends for the Azure RM are out of date. Most of the time it does get executed fine with the API version i'm using (`2021-08-01`).

The documentation also confirms this:
https://docs.microsoft.com/en-us/azure/templates/microsoft.network/2021-08-01/networkwatchers/flowlogs?tabs=bicep

I did see this with more resources, not just the networkWatcher.

**To Reproduce**
Steps to reproduce the behavior:
Deploy resources with 2021-08-01 a few times. You'll probably hit this one sooner or later.

Start by reproducing deployment of the reported networkWatchers/flowLogs resource with API version 2021-08-01 and compare the Azure RM backend versions against the linked Azure documentation. Check whether the same mismatch affects the other resources mentioned. Done means the affected backends use supported API versions and repeated deployments no longer produce NoRegisteredProviderFound errors.

Written by the indexing model from the issue text.