Fix CascadiaPackage platform mapping in OpenConsole.slnx

[katlun-lgtm]

Map '|Any CPU' to 'Win32' (not 'x86') to match the project's actual configuration names (Debug|Win32, Release|Win32). Also add an explicit '|x86 -> Win32' mapping so solution platform x86 resolves correctly.

Fixes VS warning: solution specifies a project configuration that does not exist for CascadiaPackage.wapproj.

Summary of the Pull Request

References and Relevant Issues

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

PR Checklist

• Closes #xxx
• Tests added/passed
• Documentation updated
  • If checked, please file a pull request on our docs repo and link it here: #xxx
• Schema updated (if necessary)

[DHowett]

Thanks!

[DHowett]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[carlos-zamora]

Looks like x86 is failing:
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(320,5): Error MSB3779: The processor architecture of the project being built "Win32" is not supported by the referenced SDK "Microsoft.VCLibs.Desktop, Version=14.0". Please consider changing the targeted processor architecture of your project (in Visual Studio this can be done through the Configuration Manager) to one of the architectures supported by the SDK: "x86, x64, ARM, ARM64".

[DHowett]

Yeah I was going to say, Windows App Packaging projects are special. I checked ours and it seemed like this should work, but I am not surprised that it does not.

[DHowett]

unfortunately, yes, x86 is actually the platform name used in Windows Desktop Bridge packaging projects.

[DHowett]

noted