New-AzResourceGroupDeployment and others | Rate limit of 200 per 30 seconds is exceeded

### Description

It looks like there is no rate limit handling in place for Bicep/ARM deployments.
We are experiencing a lot of failed deployments due to change over from global rate limits to bucket rate limits.

The deployment should be improved so it handles the rate limits correctly and continues the deployment without stopping.

I am not sure if this is the correct place to report this, if its incorrect please guide me to the correct channel thanks :)

### Issue script & Debug output

```PowerShell
New-AzResourceGroupDeployment
```

### Environment data

```PowerShell
N/A
```

### Module versions

```PowerShell
N/A
```

### Error output

_No response_

Start with the New-AzResourceGroupDeployment entry point and investigate the reported Bicep/ARM deployment behavior around Azure's 200-per-30-seconds bucket limit. Reproduce the failure if possible; done means deployments handle the rate limit and continue instead of stopping.

Written by the indexing model from the issue text.