New-WinGetSource fails if resource group region doesn't support classic App Insights

Brief description of your issue

Classic mode for Application Insights will be deprecated in 2024, and there's several regions that don't support it. If the created resource group is in one of those regions, the New-WinGetSource cmdlet will fail with an error like this:

Line |
 157 |          New-ARMObjects -ARMObjects $ARMObjects -RestSourcePath $RestS …
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Failed to create Azure object. 13:28:01 - The deployment 'applicationinsights' failed with error(s). Showing 1 out of 1 error(s). Status Message: Region doesn't support Classic resource mode for Application Insights
     | resources. Please use Workspace-based mode. (Code:BadRequest)  CorrelationId: daf01282-078d-4ee0-b24e-84782f2ccda5

Steps to reproduce

Run New-WinGetSource with a resource group in a region that doesn't support classic App Insights (such as westus3).

Expected behavior

Application Insights creation should use Workspace mode

Actual behavior

Failure

Environment

N/A

[RDMacLachlan]

Appreciate the insight into the limitation. This has been marked as an issue for resolution.

[aserfass-msft]

It appears this issue still exists in the latest version: https://github.com/microsoft/winget-cli-restsource/releases/tag/1.9.1