Parent resource identifier not concatenated in child extensible resources when compiled to ARM template

**Bicep version**
0.24.238

**Describe the bug**
For extensible resources, when a child resource is compiled to ARM template, the compiled child resource identifier doesn't contain the parent resource identifier, which is a different behavior for Azure resources.

```bicep
resource parentResource 'parent@1.0.0' = {
uniqueName: 'parentResourceName'

resource childResource 'child@1.0.0' = {
name: 'childResourceName'
}
}
```
Actual compiled child resource property:
```json
"properties": {
"name": "childResourceName",
}
```

Expected compiled child resource property:
```json
"properties": {
"name": "parentResourceName/childResourceName",
}
```

Notice that the `parentResourceName` is concatenated with the `childResourceName`