Fix bug in configure-continuous-deployments command and maintain developer CLI

[tjementum]

Summary & Motivation

Fix an issue where the configure-continuous-deployments command failed when the az CLI threw an exception. Previously, these exceptions were handled correctly, but a recent update to how the CLI executes commands introduced an issue where errors were not always caught properly. This is now fixed.

Additionally, Azure region identifiers have been improved. The previous region abbreviations (e.g., gwc for Germany West Central) were not always intuitive. These have been updated to use country-specific ISO codes where applicable (e.g., us, ca, uk), and regional codes for areas with shared data sovereignty rules (e.g., eu for the European Union, as for Southeast Asia).

Other general maintenance updates have also been made to the developer CLI:

• Ensure consistency in CLI descriptions and output messages by standardizing trailing periods.
• Upgrade all NuGet packages, .NET SDK, and JetBrains tools to their latest versions.
• Fix static code analysis warnings from SonarQube and JetBrains.
• Remove ConfigurationSettings.ConfigurationSetting, which has been marked as obsolete for a while.
• Add an explicit reference to System.IO.Pipelines Version=9.0.1 to avoid having to double build when the CLI detects changes.

Checklist

• I have added tests, or done manual regression tests
• I have updated the documentation, if necessary

[linear]

PP-317 The configure-continuous-deployments CLI command fails when the az CLI throws an exception

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud