Windows App SDK 2.0 installation requires admin elevation

Nobody has claimed this yet.

### Describe the bug

Hi,

after the WinML update in our desktop app (Voicemod), users who need Windows App SDK 2.0 are prompted for administrator privileges to install it. This is unexpected from the user's perspective and has caused confusion.

Our current flow is:
- When the user enables the NPU toggle, we check whether Windows App SDK 2.0 is installed.
- If it is not installed, we notify the user, download the appropriate installer:
https://aka.ms/windowsappsdk/2.0/2.0.1/windowsappruntimeinstall-x64.exe
https://aka.ms/windowsappsdk/2.0/2.0.1/windowsappruntimeinstall-arm64.exe
- We launch the installer using ShellExecuteExW.

Is this the expected behavior? Is there a recommended flow that avoids requesting administrator privileges at this point?

Let us know if you need mor information.

Thanks,
Carles

### Steps to reproduce the bug

1. Download and Install Voicemod on a machine without Windows App SDK 2.0.
2. Open Settings (left bar).
3. Enable the NPU toggle.

### Expected behavior

_No response_

### Screenshots

_No response_

### NuGet package version

2.0.1

### Packaging type

_No response_

### Windows version

_No response_

### IDE

_No response_

### Additional context

_No response_

Start by reproducing the NPU-toggle flow on a machine without Windows App SDK 2.0, using the Windows App Runtime 2.0.1 installers and the ShellExecuteExW launch path described in the issue. Determine whether administrator elevation is expected and document or identify a supported installation flow that addresses the reported behavior.

Written by the indexing model from the issue text.