Workspaces: PWA apps should not necessarily configure profile to launch.

[vanzue]

Summary of the Pull Request

Workspace support for pwa is now limited, it is tight to specific Profile launch. If you create a pwa app with a profile other than "Default", launch will fail. Then you have to manually configure that profile to launch.
This pr fix it by launching with shell:appsfolder\appusermodelId

PR Checklist

• Closes: PWA doesn't launch with Workspace #36384
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

• Create a new workspace with a pwa app(Other than default profile) should be no problem.
• Existing workspace with a pwa(default profile and other profile) should launch successfully without problem

1. with pt version 91.1, create a loop pwa with "Profile 1" instead of "Default" in edge.
2. capture and launch actually launch the edge instead of loop
3. Create profile with this impl and launch
4. Launch pwa successfully

[Copilot]

Pull Request Overview

This PR fixes a launch failure for PWAs when using a non‐default profile by switching to using the AppUserModelId from a WindowUtils utility and adding version handling to control the launch path. Key changes include:

• Replacing calls to PwaHelper’s GetAUMIDFromWindow with the new Utils::GetAUMIDFromWindow method.
• Introducing a version field for applications to control launch behavior.
• Updating project files and related modules (WorkspacesData, WorkspacesEditor, etc.) to propagate and use the new version information.

Reviewed Changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
WindowArranger.cpp	Updated to use Utils::GetAUMIDFromWindow for retrieving the AUMID.
SnapshotUtils.cpp	Modified to assign appUserModelId and version from the window AUMID and JSON data.
WorkspacesLib.vcxproj & .filters	Added new WindowUtils and StringUtils source files to the project.
WorkspacesData.h/.cpp	Added a new version field to support versioned launch behavior.
WindowUtils.{h,cpp}	New utility for retrieving window properties including the AUMID.
AppLauncher.cpp	Updated launch logic to parse version and decide the correct launch path.
WorkspacesEditor files	Propagated the version property into workspace editor models and serialization.

Comments suppressed due to low confidence (1)

src/modules/Workspaces/WorkspacesLib/WorkspacesData.h:37

• [nitpick] Clarify the comment for the version field to indicate whether the empty version string should default to '1' and explain the rationale behind this default behavior.

// empty to 1,

[yeelam-gordon]

I follow the logic, basically adding a virtual version to use the new behavior or launch or not.

[vanzue]

I follow the logic, basically adding a virtual version to use the new behavior or launch or not.

Thanks for review!