what-if result inaccuracies across scope boundaries.

### Discussed in https://github.com/Azure/bicep/discussions/10332

---
more information

@JoshuaXu-Wen

##### Adding code in case anyone else wants to test this out OR view the scope specific issue examples

#### main. Bicep - resource group scoped deployment
```bicep
param location string = 'eastus'
param rgName string = 'myRG2'

// targetScope = 'subscription'

module RG 'temp.bicep' = {
name: 'rg'
scope: subscription()
params: {
location: location
rgName: rgName
}
}

output rgname string = RG.outputs.RGName
```
#### temp.bicep
```bicep
param rgName string
param location string
param tags object = {}

targetScope = 'subscription'

resource RG 'Microsoft.Resources/resourceGroups@2022-09-01' = {
name: rgName
location: location
tags: tags
properties: {}
}

output RGName string = RG.name
```

1) If the resource group does not exist, you will get an error, since going across scopes it is unable to complete the `what-if`
> 'The request to predict template deployment changes to scope '/subscriptions/4185fa9b-f470-466a-b3ae-8e6c3314a543/resourceGroups/AEU1-PE-CTL-RG-D1' has failed due to a resource error. 🟥

2) if the resource group does exist, it doesn't detect it and it shows it will create it. 🟥


#### It appears this is a result from going across scopes: Resource Group --> Subscription --> Resource group.

#### The workaround

1) Deploy in the subscription scope initially and what-if works as expected

```bicep
param location string = 'eastus'
param rgName string = 'myRG2'

targetScope = 'subscription'

module RG 'temp.bicep' = {
name: 'rg'
// scope: subscription()
params: {
location: location
rgName: rgName
}
}

output rgname string = RG.outputs.RGName
```

1) When no RG exists - corretly shows it will be created ✅


2) When the RG exists - correctly shows it will be ignored ✅


Start with the main Bicep and temp.bicep examples in the issue, using a subscription-to-resource-group deployment and testing both an existing and missing resource group. Compare what-if output with the documented subscription-scoped workaround. Done means cross-scope what-if no longer reports an incorrect error or creation result.

Written by the indexing model from the issue text.