Wrong app sdk version number reported if another application directory with an older app sdk is added to PATH

Nobody has claimed this yet.

### Describe the bug

The Microsoft.Windows.ApplicationModel.WindowsAppRuntime.ReleaseInfo api reports the wrong version number in the following scenario:

- The app is unpackaged and not self-contained
- Another application (example: powertoys) is installed and its installation directory is added to the PATH variable and it contains a copy of the app sdk

In this case Microsoft.WindowsAppRuntime.Insights.Resource.dll is loaded from the directory of the other installed application and the wrong version number is reported.

### Steps to reproduce the bug

1. Install powertoys
2. Create an unpackaged (not self-contained) app sdk application
3. Check the return value of Microsoft.Windows.ApplicationModel.WindowsAppRuntime.ReleaseInfo

### Expected behavior

The app sdk version number should not be influenced by installing another (unrelated) application.

### Screenshots

_No response_

### NuGet package version

Windows App SDK 1.8.2: 1.8.251003001

### Packaging type

Unpackaged

### Windows version

Windows 11 version 24H2 (26100, June 2025 Update)

### IDE

Visual Studio 2022

### Additional context

_No response_

Start with the Microsoft.Windows.ApplicationModel.WindowsAppRuntime.ReleaseInfo API and Microsoft.WindowsAppRuntime.Insights.Resource.dll loading behavior. Reproduce the issue using the listed unpackaged, non-self-contained setup with PowerToys on PATH; done means the reported Windows App SDK version is unaffected by the other application's directory.

Written by the indexing model from the issue text.