Microsoft.Web/sites: endToEndEncryptionEnabled is not allowed - Warning

### Resource Type

Microsoft.Web/sites

### Api Version

2023-01-01

### Issue Type

Missing property(s)

### Other Notes

This property is available in the GUI and supported by ARM, if you use the property the setting works fine it just gives you a warning. My example Bicep deploys with out issue just need to update so it doesn't warn with "Property is not allowed"

### Bicep Repro

resource appService_r 'Microsoft.Web/sites@2023-01-01' = {
name: appServiceName
location: location
kind: webAppKind
tags: tags
identity: {
type: 'SystemAssigned'
}
properties:{
endToEndEncryptionEnabled: true
serverFarmId: appServicePlan_r.id
reserved: true
isXenon: false
hyperV: false
scmSiteAlsoStopped: false
clientAffinityEnabled: false
clientCertEnabled: false
hostNamesDisabled: false
containerSize: 0
dailyMemoryTimeQuota: 0
httpsOnly: true
virtualNetworkSubnetId: subnetId
siteConfig: {
minTlsVersion: '1.2'
minTlsCipherSuite: 'TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256'
appSettings: [
{
name: 'FLASK_ENV'
value: 'production-${flaskClient}'
}
{
name: 'AZURE_POSTGRESQL_CONNECTIONSTRING'
value: AZURE_POSTGRESQL_CONNECTIONSTRING
}
]

}
}
}

### Confirm

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

Start by locating the Microsoft.Web/sites type definition for API version 2023-01-01 and compare its allowed properties with the reported Bicep repro. Verify that endToEndEncryptionEnabled is accepted without a "Property is not allowed" warning while the deployment continues to work.

Written by the indexing model from the issue text.