Allow dependsOn for existing resources

[jeskew]

Resolves #13596

Microsoft Reviewers: Open in CodeFlow

[github-actions]

Test this change out locally with the following install scripts (Action run 11633757585)

VSCode

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-vsix.sh) --run-id 11633757585

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-vsix.ps1) } -RunId 11633757585"

Azure CLI

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-cli.sh) --run-id 11633757585

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-cli.ps1) } -RunId 11633757585"

[github-actions]

Dotnet Test Results

    72 files   -     36      72 suites   - 36   28m 59s ⏱️ - 12m 39s
11 379 tests  -     23  11 379 ✅  -     23  0 💤 ±0  0 ❌ ±0 
26 489 runs   - 13 234  26 489 ✅  - 13 234  0 💤 ±0  0 ❌ ±0 

Results for commit b435471. ± Comparison against base commit 6bf7499.

[levimatheri]

the presence of any existing resources with explicit dependencies should result in Bicep using symbolic name compilation

Going by the above comment on the linked issue. I was curious: where are we detecting the dependsOn on existing in order to "auto-upgrade" to use symbolic names? Not seeing that in this PR...

[jeskew]

the presence of any existing resources with explicit dependencies should result in Bicep using symbolic name compilation

Going by the above comment on the linked issue. I was curious: where are we detecting the dependsOn on existing in order to "auto-upgrade" to use symbolic names? Not seeing that in this PR...

That change ended up being unnecessary. The dependency inference code in Bicep will take a dependency on an existing resource's transitive dependencies, so the dependsOn ends up getting respected.