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

[jason-dou]

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.

resource parentResource '[email protected]' = {
  uniqueName: 'parentResourceName'

  resource childResource '[email protected]' = {
    name: 'childResourceName'
  }
} 

Actual compiled child resource property:

"properties": {
      "name": "childResourceName",
}

Expected compiled child resource property:

"properties": {
      "name": "parentResourceName/childResourceName",
}

Notice that the parentResourceName is concatenated with the childResourceName

[dkershaw10]

This is pretty critical for us as Graph has many nested/child resources, and we want the same Bicep authoring experience as other types.