AzFrontDoor and RulesEngine Dependencies

**Bicep version**
Bicep CLI version 0.4.63 (7ebed03284)

**Describe the bug**
Dependency loop.
Building new Azure Front Door and Rules Engine. The Routing Rule reference for the Rules Engine doesn't exist until the Azure Front Door is built, but building the Azure Front Door fails because the referenced Rules Engine doesn't exist yet.

**To Reproduce**
build Azure Front Door that has a routing rule reference to a rules engine that exists as a child resource of that same azure front door object you are attempting to build.

**Additional context**
Setting `dependsOn` on the `rulesEngine` resource and commenting out the reference in the `routingRules` allows you to build the Azure Front Door. Then I can uncomment the `rulesEngine` reference, apply again, and it will now find the AFD associate the new `rulesEngine`.

reference in the routing rules of AFD resource

```bicep
routingRules: [
{
name: appName
properties: {
rulesEngine: {
id: resourceId('Microsoft.Network/frontDoors/rulesEngines', fdName, rulesEngineName)
}
```

reference of the fdRulesEngine resource

```bicep
resource fdRulesEngine 'Microsoft.Network/frontDoors/rulesEngines@2020-05-01' = {
//note: rules-engine resource specific scenario where the parent (afd) resource name needs to be included in child name
name: '${fdName}/${rulesEngineName}'`
```