`desktop:ExecutionAlias` declared in `Package.appxmanifest` not working on Windows Server 2019

Nobody has claimed this yet.

### Describe the bug

A few users of my app reported that they cannot launch my app on their Windows Server. After some digging, I found on normal Windows 10/11, if the app declares an `desktop:ExecutionAlias`, it will create an entry in `%localappdata%\Microsoft\WindowsApps\`. But the folder is empty on Windows Server (2019 17763, to be specific).

I am not sure whether this issue happens to all Windows Server version. But on 17763, I write a demo to test that and it's 100% reproducible.

### Steps to reproduce the bug

1. Create a new WinUI3 C++ project, packaged
2. Add this under the `Application` node in `Package.appxmanifest`
```xml







```
3. Build a msix package, deploy on Windows Server. Run `winuiBugTest.exe`, and it will report the file is not found.

### Expected behavior

The app should run

### Screenshots


### NuGet package version

Windows App SDK 1.6.3: 1.6.241114003

### Packaging type

Packaged (MSIX)

### Windows version

_No response_

### IDE

Visual Studio 2022

### Additional context
Using `uap5` also does not work. And I don't even know what are the differences
```xml





```

[repro](https://github.com/HO-COOH/WinUI-Bug/tree/main/22-ExecutionAliasNotFound)

Start with the desktop:ExecutionAlias declaration in Package.appxmanifest and the linked repro at 22-ExecutionAliasNotFound. Reproduce the packaged MSIX behavior on Windows Server 2019 build 17763, then compare it with Windows 10 or 11 and inspect the Windows App SDK packaging or deployment path involved. Done means identifying the compatibility cause or documenting a confirmed platform limitation and supported behavior.

Written by the indexing model from the issue text.