Update UseResourceIdFunctionsRule to account for nullable and aggregate types

[jeskew]

Resolves #12419

The UseResourceIdFunctionsRule linter rule doesn't report any diagnostics if a parameter is supplied for a resource property that expects a resource ID, but this exemption doesn't apply directly to parameter properties. This didn't raise any issues in the past because prior to the introduction of user-defined types, parameter properties would always have an any type, and the linter rule will only raise diagnostics on string-typed values.

Microsoft Reviewers: Open in CodeFlow

[github-actions]

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

VSCode

• Mac/Linux

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

• Windows

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

Azure CLI

• Mac/Linux

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

• Windows

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

[github-actions]

Test Results

     132 files  ±  0       132 suites  ±0   4h 47m 8s ⏱️ - 14m 15s
10 690 tests +  4  10 690 ✔️ +  4  0 💤 ±0  0 ❌ ±0 
51 655 runs  +16  51 655 ✔️ +16  0 💤 ±0  0 ❌ ±0 

Results for commit 34da0ae. ± Comparison against base commit 8171b4c.

♻️ This comment has been updated with latest results.