Harden Windows E2E app install flow

[StuartFerguson]

The Windows E2E workflow was hard-coded to a single generated Install.ps1 path, which made it brittle when package output location/name changed. This updates the install step to match the navigation workflow’s resilient package discovery and installation behavior.

• Dynamic package discovery
  • Locates AppPackages from the two expected build outputs instead of assuming one fixed path.
• Script-first install
  • Runs Install.ps1 when present, preserving the existing packaged install flow.
• MSIX fallback
  • Falls back to Add-AppxPackage when only the .msix is available.

$candidatePaths = @(
  (Join-Path $env:GITHUB_WORKSPACE "TransactionProcessor.Mobile\AppPackages"),
  (Join-Path $env:GITHUB_WORKSPACE "TransactionProcessor.Mobile\bin\Release\net10.0-windows10.0.19041.0\win-x64\AppPackages")
)

$installScript = Get-ChildItem -Path $appPackagesPath -Recurse -Filter Install.ps1 | Select-Object -First 1
if ($null -ne $installScript) {
  & $installScript.FullName -Force
} else {
  $msixPackage = Get-ChildItem -Path $appPackagesPath -Recurse -Filter *.msix | Select-Object -First 1
  Add-AppxPackage -Path $msixPackage.FullName -ForceApplicationShutdown
}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 21 complexity · 0 duplication

Metric	Results
Complexity	21
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}