Parallel access to Microsoft.Keyvaults

**Is your feature request related to a problem? Please describe.**
In a bicep file that in parallel creates modules that in parallel set keyvault secrets we hit this runtime problem:

```json
{
"status": "Failed",
"error": {
"code": "ConflictError",
"message": "A conflict occurred that prevented the operation from completing. The operation failed because the Microsoft.KeyVault.UnifiedStorage.Core.DomainModel.ResourceId 'Key Vault' changed from the point the operation began. This can happen if parallel operations are being performed on the Microsoft.KeyVault.UnifiedStorage.Core.DomainModel.ResourceId. To prevent this error, serialize the operations so that only one operation is performed on the Microsoft.KeyVault.UnifiedStorage.Core.DomainModel.ResourceId at a time. Follow this link for more information: https://go.microsoft.com/fwlink/?linkid=2147741"
}
}
```

**Describe the solution you'd like**
Is there a way to detect this in Bicep and signal a potential issue? Should `@batchSize(1)` be suggested in such cases?

The issue names no repository files, tests, or entry points. Start by reviewing how Bicep handles parallel module deployments and the @batchSize(1) decorator, then determine whether this Key Vault conflict can be detected statically. Done should define a clear diagnostic or recommendation and tests for the reported deployment pattern.

Written by the indexing model from the issue text.