Feature proposal:Hope to increase the resolution of resources.pri in the language resource package

### Describe the bug

Feature proposal:Feature proposal:Hope to increase the resolution of resources.pri in the language resource package

##### ----------------------------------

希望能增加对语言资源包的 resources.pri 的解析

----------------------------------


目前可以通过 ```ResourceLoader``` API 来读取本地 ```resources.pri``` 的文件信息，但是部分安装包里面包含语言资源包，里面单独存放了特定语言下的 ```resources.pri```。如果使用 ```makepri.exe``` 解析，需要使用 ```/ExternalSchema``` 参数，并添加应用包的 ```resources.pri``` 才能解析成功。所以希望 ```WASDK``` 在 ```MRT Core``` 也能增加相应的功能。

##### ----------------------------------

Currently, you can read the local resources.pri file information through the ```ResourceLoader``` API. However, some installation packages contain language resource packages, which separately store ```resources.pri``` in a specific language. If ```makepri.exe``` is used for parsing, you need to use the ```/ExternalSchema``` parameter and add ```resources.pri``` of the application package to make the parsing successful. Therefore, it is hoped that ```WASDK``` can also add corresponding functions in ```MRT Core```.

----------------------------------

For example, the simplified Chinese resource file of Notepad and the resource file corresponding to the Notepad installation package

##### ----------------------------------

比如，记事本的简体中文资源文件和记事本安装包对应的资源文件


### Steps to reproduce the bug

See description

### Expected behavior

See description

### Screenshots

See description

### NuGet package version

Windows App SDK 1.6.3: 1.6.250108002

### Packaging type

Packaged (MSIX)

### Windows version

Windows 11 version 24H2 (22621, October 2024 Update)

### IDE

Visual Studio 2022

### Additional context

None

Start with the ResourceLoader API and MRT Core behavior described in the issue, then compare how makepri.exe uses /ExternalSchema with an application package resources.pri and a language package resources.pri. Done would mean defining and implementing corresponding Windows App SDK support for parsing these language resources, with the expected API and scope clarified first.

Written by the indexing model from the issue text.