[Feature Request]: Enable utility version control in CI

[AlexanderSehr]

Description

The CARML CI currently does not provide out-of-the-gate capabilities to control which version of the uses tools (for example) are installed on the agents. As this can lead to issues (ref: #2641 #2659), we should implement a logic that optionally allows just that.

The idea could be 3 settings in the settings.yml:

• AzCLI version

• PowerShell version

• Bicep version

• and if they're set to '*' or 'latest' we could install latest.

The Set-EnvironmentOnAgent script already surfaces the used versions and in parts the code to install specific versions of e.g. Bicep.

In a first step we could concentrate on installing/updating - and in a second step on downgrading (if required)

[eriqua]

Start with a PoC covering both ADO and GH Open a follow up issue to cover edge cases and remaining work, e.g.,

• what should be the behavior for non existing versions
• what should be the behavior for versions lower than the one currently used by runners