Microsoft.DBforMySQL/flexibleServers not idempotent on redeploy

**Bicep version**
Bicep CLI version 0.23.1 (b02de2da48)

**Describe the bug**
Currently deploying a very basic Microsoft.DBforMySQL/flexibleServers resource. Deploying the same and not making a change results in an error:

{
"code": "InternalServerError",
"message": "An unexpected error occured while processing the request. Tracking ID: IDNUMBER"
}

**To Reproduce**
Steps to reproduce the behavior:

Module:

**dbForMySQLFlexibleServers.bicep**

```
param name string
param location string
param tags object
param sku object
param properties object

resource dbforMySqlFlexibleServer 'Microsoft.DBforMySQL/flexibleServers@2022-09-30-preview' = {
name: name
location: location
tags: tags
sku: sku
properties: properties
}
```

Main:
**main.bicep**

// database server

```
module dbs 'modules/dbForMySQLFlexibleServers.bicep' = {
scope: resourceGroup(rg.name)
name: 'dbs-${namePrefix}'
params: {
name: 'dbs-${namePrefix}'
location: location
tags: tags
sku: dbsSku
properties: {
createMode: 'Default'
dataencryption: {}
administratorLogin: dbAdminUsername
administratorLoginPassword: dbAdminPassword
storage: {
storageSizeGB: 20
iops: 400
autoGrow: 'Enabled'
autoIoScaling: 'Enabled'
logOnDisk: 'Disabled'
}
version: '8.0.21'
availabilityZone: 2
network: {
publicNetworkAccess: 'Enabled'
}
backup: {
backupRetentionDays: 7
geoRedundantBackup: 'Disabled'
}
highAvailability: {
mode: 'Disabled'
}
}
}
}
```

Tried a few changes, i.e. copy the ARM from the portal, etc but still fails.

Begin with the supplied dbForMySQLFlexibleServers.bicep module and main.bicep deployment; reproduce an unchanged redeploy using Bicep CLI 0.23.1 and Microsoft.DBforMySQL/flexibleServers@2022-09-30-preview. Done means identifying a repository-supported correction or documenting that the failure is in the Azure resource API, with a repeatable reproduction.

Written by the indexing model from the issue text.