Add VersionChecker to detect and warn about newer Bicep CLI installations

[polatengin]

VersionChecker helper scans well-known install locations, runs bicep --version to parse versions, and reports any installations newer than the running CLI.

Fixes #5070

Description

Well-known installation locations checked:

~/.bicep/bin (default location)
~/.azure/bin (Azure CLI installation location)

Windows-specific:

• C:\Program Files\Bicep CLI
• C:\Program Files (x86)\Bicep CLI
• All directories in the PATH environment variable

Linux-specific:

• /usr/local/bin
• /usr/bin/
• All directories in the PATH environment variable

Example Usage

Run any bicep command. You may see this warning in the terminal;

Warning: You are running Bicep CLI version 0.38.1, but newer version(s) are installed on this system:
  - Version 0.40.23 at /usr/local/bin/bicep
  - Version 0.39.47 at ~/.azure/bin/bicep

Checklist

• I have read and adhere to the contribution guide.

Microsoft Reviewers: Open in CodeFlow

[github-actions]

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

VSCode

• Mac/Linux

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

• Windows

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

Azure CLI

• Mac/Linux

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

• Windows

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

[github-actions]

Dotnet Test Results

   102 files   -     42     102 suites   - 42   41m 1s ⏱️ - 35m 23s
12 554 tests +    16  12 554 ✅ +    16  0 💤 ±0  0 ❌ ±0 
28 853 runs   - 14 333  28 853 ✅  - 14 333  0 💤 ±0  0 ❌ ±0 

Results for commit f8c3d61. ± Comparison against base commit 8ea021c.

This pull request removes 1954 and adds 690 tests. Note that renamed tests count towards both.

		nestedProp1: 1
		nestedProp2: 2
		prop1: true
		prop2: false
	1
	2
	\$'")
	prop1: true
	prop2: false
…

Bicep.Cli.IntegrationTests.BuildParamsCommandTests ‑ BuildParams_ResourceInputType_ArrayOfResources_Succeeds
Bicep.Cli.IntegrationTests.BuildParamsCommandTests ‑ BuildParams_ResourceInputType_ComplexNestedObject_Succeeds
Bicep.Cli.IntegrationTests.BuildParamsCommandTests ‑ BuildParams_ResourceInputType_NestedProperty_Succeeds
Bicep.Cli.IntegrationTests.BuildParamsCommandTests ‑ BuildParams_ResourceInputType_WithValidObject_Succeeds
Bicep.Cli.UnitTests.Helpers.VersionCheckerTests ‑ CheckForNewerVersionsAsync_ShouldCheckWindowsLocations_OnWindows
Bicep.Cli.UnitTests.Helpers.VersionCheckerTests ‑ CheckForNewerVersionsAsync_ShouldHandleInvalidVersions
Bicep.Cli.UnitTests.Helpers.VersionCheckerTests ‑ CheckForNewerVersionsAsync_ShouldHandleNonExistentDirectories
Bicep.Cli.UnitTests.Helpers.VersionCheckerTests ‑ CheckForNewerVersionsAsync_ShouldNotRun_WhenShouldCheckIsFalse
Bicep.Cli.UnitTests.Helpers.VersionCheckerTests ‑ CheckForNewerVersionsAsync_ShouldNotWarn_WhenNoNewerVersionsFound
Bicep.Cli.UnitTests.Helpers.VersionCheckerTests ‑ CheckForNewerVersionsAsync_ShouldNotWarn_WhenOlderVersionFound
…

♻️ This comment has been updated with latest results.

[anthony-c-martin]

This is a pretty major behavioral change, and could have serious performance implications that we need to think through, as well as product design implications. At minimum, I think we need to cover this as a topic in Bicep Discussions before continuing on with the change.

Generally, I think my feeling with doing this work is that the cons outweigh the pros. Issue #5070 was created a long time ago, and since then, I don't think it's been as much of a problem as we imagined it being.