Microsoft.DBforPostgreSQL/serverGroupsv2: no support for databaseName property

### Resource Type

Microsoft.DBforPostgreSQL/serverGroupsv2

### Api Version

2022-11-08

### Issue Type

Missing property(s)

### Other Notes

Unable to use bicep to set database name of the Cosmosdb Postgres server. This is a solution breaking issue.

### Bicep Repro

resource coredb 'Microsoft.DBforPostgreSQL/serverGroupsv2@2022-11-08' = {
name: clusterName
location: location
tags: {}
properties: {
databaseName: 'global-core' // <--- This is not valid in bicep but is the proper property in the deployment json template. This does not deploy properly and defaults to 'citus'
administratorLoginPassword: administratorLoginPassword
coordinatorServerEdition: coordinatorServerEdition
coordinatorVCores: coordinatorVCores
coordinatorStorageQuotaInMb: coordinatorStorageQuotaInMb
enableShardsOnCoordinator: enableShardsOnCoordinator
nodeCount: nodeCount
nodeServerEdition: nodeServerEdition
nodeVCores: nodeVCores
nodeStorageQuotaInMb: nodeStorageQuotaInMb
enableHa: enableHa
coordinatorEnablePublicIpAccess: coordinatorEnablePublicIpAccess
nodeEnablePublicIpAccess: nodeEnablePublicIpAccess
citusVersion: citusVersion
postgresqlVersion: postgresqlVersion
// preferredPrimaryZone: availabilityZone
}
}
}

### Confirm

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

Start with the type definition for Microsoft.DBforPostgreSQL/serverGroupsv2 at API version 2022-11-08, using the Bicep reproduction as the expected input. Verify the resource schema accepts databaseName and run the relevant type-generation or validation checks; done means Bicep no longer rejects the property and deployments preserve the requested database name.

Written by the indexing model from the issue text.