Fix deploy pane when deploying .bicep files directly

[anthony-c-martin]

As part of the local deployment implementation, I apparently completely removed the ability for the deployment pane to deploy a non-local .bicep file 🤦. This PR fixes that.

The changes in this PR:

• Fixes deployment through the deploy pane if the user is referencing a .bicep file directly.
• As part of testing this, I noticed we're actually missing validation for a using statement referencing a broken file. I've updated this to bring it in line with behavior for a module statement referencing a broken file.
• Fixes the issue where a cryptic error appears in local-deploy mode if the .bicep file is invalid.
• Fixes an issue where we're not logging the artifact reference properly in error messages (missing a .ToString() implementation).

Microsoft Reviewers: Open in CodeFlow

[github-actions]

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

VSCode

• Mac/Linux

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

• Windows

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

Azure CLI

• Mac/Linux

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

• Windows

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

[github-actions]

Dotnet Test Results

    72 files   -     36      72 suites   - 36   23m 42s ⏱️ - 11m 12s
10 966 tests  -     11  10 966 ✅  -     11  0 💤 ±0  0 ❌ ±0 
25 812 runs   - 12 899  25 812 ✅  - 12 899  0 💤 ±0  0 ❌ ±0 

Results for commit 48a4d4f. ± Comparison against base commit f1c7212.

♻️ This comment has been updated with latest results.