Microsoft.Automation/automationAccounts/configurations require location property however Bicep does not include ti

**Bicep version**
Bicep CLI version 0.4.1124 (66c84c8ee5)

**Describe the bug**
To deploy Microsoft.Automation/automationAccounts/configurations a number of properties are required including location, even though it is a read only property. Bicep does not support the property however in ARM this is a property and during deployment this is expected.

Example code:

`resource automationAccountsConfiguration 'Microsoft.Automation/automationAccounts/configurations@2019-06-01' = {
parent: automationAccounts
name: 'ExampleDSCConfiguration'
}`

Error on the portal:

`{
"status": "Failed",
"error": {
"code": "LocationRequired",
"message": "The location property is required for this definition."
}
}`

**To Reproduce**
Deploy the below code using Bicep:

```
resource automationAccounts 'Microsoft.Automation/automationAccounts@2021-06-22' = {
name: 'ExampleAutomation'
location: location
identity: {
type: 'SystemAssigned'
}
properties: {
encryption: {
identity: {}
keySource: 'Microsoft.Automation'
}
sku: {
name: 'Basic'
}
}
tags: {}
}

resource automationAccountsConfiguration 'Microsoft.Automation/automationAccounts/configurations@2019-06-01' = {
parent: automationAccounts
name: 'ExampleDSC'
}
```

Reproduce the deployment with Bicep CLI 0.4.1124 using the Microsoft.Automation/automationAccounts/configurations@2019-06-01 declaration shown in the issue. Inspect how this resource type represents required properties, especially location, and verify that the example deploys without the LocationRequired error once the issue is addressed.

Written by the indexing model from the issue text.