Remove scope filter from being applied to portables

[ryfu-msft]

If the --scope argument is present when installing a portable package, the command will fail if the incorrect scope is not present for a portable installer. This is the wrong behavior as the scope field in the manifest should not apply to portable packages.

To resolve this issue, I have removed the applied scope filter if the installerType is portable (and also for msix).

Changes:

• Bypass scope filter if the installertype is portable (or msix) using a semantic function
• Added an admin requirement to portable install if the scope is Machine
• Fixed several discrepancies in the portableAppUserRoot and portableAppMachineRoot naming/documentation
• Added unit and E2E tests to verify that portable install works as expected when scope arguments are provided.

Microsoft Reviewers: Open in CodeFlow

[Trenly]

It seems like theres a duplicated call here, but only in certain scenarios. When dev mode is disabled, it checks for admin to ensure synlink creation, then checks for admin again if running a machine scope install.

I’m sure that this will work, I’m just wondering if maybe theres a better way to handle checking the elevation level?

[JohnMcPMS]

It is less efficient, but EnsureSymlinkCreationPrivilege is planned to be temporary, so it is easier to keep it separated.

[ryfu-msft]

EnsureSymlinkCreationPrivilege is meant to be a temporary check to handle the special case where a user may have developer mode off. I expect that this check will be removed once we fully address this issue in 1.4, so I decided to keep these as separate checks for better clarity and cleanup in the near future.

[ryfu-msft]

Guess I needed to refresh the page :)