Synapse trustedServiceBypassEnabled setting not deploying through Bicep.

**Bicep version**
0.12.40

**Describe the bug**
Deploy Synapse Workspace through Bicep with trustedServiceBypassEnabled set to true. After deployment otherwise successfully finishes, the setting is "false", which is the opposite of what is declared in the template. Expected "_Allow Azure services and resources to access this workspace_" to be enabled.

**To Reproduce**
Deploy Synapse Workspace resource through a Bicep template file using resource group scope in either Complete or Incremental mode.

```bicep
resource synapseWorkspace 'Microsoft.Synapse/workspaces@2021-06-01' = {
name: synapseWorkspaceName
location: azureLocation
identity: {
type: 'SystemAssigned'
}
properties: {
azureADOnlyAuthentication: true
cspWorkspaceAdminProperties: {
initialWorkspaceAdminObjectId: ''
}
defaultDataLakeStorage: {
accountUrl: .properties.primaryEndpoints.dfs
createManagedPrivateEndpoint: false
filesystem: 'synapse'
}
publicNetworkAccess: 'Enabled'
sqlAdministratorLogin: ''
sqlAdministratorLoginPassword: ''
trustedServiceBypassEnabled: true
}
}
```

**Additional context**
Also tried the trustedServiceByPassConfiguration resource type as described in documentation:
https://learn.microsoft.com/en-us/azure/templates/microsoft.synapse/workspaces/trustedservicebypassconfiguration?pivots=deployment-language-bicep

However that resulted in a _NullRequest: Request was deserialized as null_ error.

Start by reproducing the deployment from the Bicep template shown in the issue, checking trustedServiceBypassEnabled after completion in both Complete and Incremental modes. Compare that behavior with the trustedServiceBypassConfiguration resource type in the linked documentation and its reported NullRequest error. Done means the declared setting deploys as true and the alternate resource form no longer fails.

Written by the indexing model from the issue text.