Invalid what-if warning on bicep deploy

### Resource Type

Private Endpoint

### Api Version

bicep deployment

### Issue Type

Other

### Other Notes

Using the what-if flag on an az deployment group create for a bicep containing existing privateEndpoints produces the following output

~ __Microsoft.Network/privateEndpoints/[privateendpoint]
- properties.isIPv6EnabledPrivateEndpoint: false

To get rid of this I added this property, which works, but produces the following warning:

Warning BCP037: The property "isIPv6EnabledPrivateEndpoint" is not allowed on objects of type "PrivateEndpointProperties". Permissible properties include "applicationSecurityGroups", "customDnsConfigs", "customNetworkInterfaceName", "ipConfigurations", "manualPrivateLinkServiceConnections". If this is a resource type definition inaccuracy, report it using https://aka.ms/bicep-type-issues [https://aka.ms/bicep/core-diagnostics#BCP037]

### Bicep Repro

Here is template you will have to replace name and ids to match your environment.

```bicep
resource privateEndpoint 'Microsoft.Network/privateEndpoints@2024-01-01' = {
name: privateEndpointConnectionName
location: resourceGroup().location
properties: {
privateLinkServiceConnections: [
{
name: privateEndpointName
properties: {
privateLinkServiceId: eventGridTopic.id
groupIds: ['topic']
}
}
]
subnet: {
id: subnet.id
}
}
}
```

### Confirm

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

Start by reproducing the supplied Private Endpoint template with `az deployment group create` using the `what-if` flag. Compare the reported `isIPv6EnabledPrivateEndpoint` difference with the BCP037 warning and the permitted `PrivateEndpointProperties` fields; done means the type definition and what-if output no longer contradict each other.

Written by the indexing model from the issue text.