missing Microsoft.Network/virtualNetworks.properties.virtualNetworkPeerings.properties.peerCompleteVnets

### Resource Type

Microsoft.Network/virtualNetworks

### Api Version

2023-09-01

### Issue Type

Type is unavailable

### Other Notes

```
az deployment group what-if --name integration-platform --resource-group mm --template-file some-file : Warning BCP037: The property "peerCompleteVnets" is not allowed on objects of type "VirtualNetworkPeeringPropertiesFormat". Permissible properties include "peeringState", "peeringSyncLevel", "remoteAddressSpace", "remoteBgpCommunities", "remoteVirtualNetwork", "remoteVirtualNetworkAddressSpace". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]

Note: The result may contain false positive predictions (noise).
```

the `what-if` is showing this property:

```

~ Microsoft.Network/virtualNetworks/MM_Vnet [2023-09-01]
~ properties.virtualNetworkPeerings: [
~ 0:

- properties.peerCompleteVnets: true
...
```

### Bicep Repro

_No response_

### Confirm

- [X] I have read the troubleshooting guide and looked for duplicates.

Start with the Microsoft.Network virtualNetworks type definition for API version 2023-09-01 and trace how VirtualNetworkPeeringPropertiesFormat is sourced or generated. Check how the reported peerCompleteVnets property is represented, then validate the result with the az deployment group what-if command and confirm the BCP037 warning is resolved.

Written by the indexing model from the issue text.