Please remove WASDK Dynamic dependencies packaged app limitation

Please remove WASDK Dynamic dependencies packaged app limitation

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

请删除 WASDK 动态依赖项打包的应用程序限制

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

My project uses WinUI 2 and WinUI 3 together, WinUI 2 and WinUI 3 contain both Microshot.ui.xaml.dll dependency libraries, and I need to use the MSIX dynamic dependency API to resolve this conflict. When I use the Windows App SDK dynamic dependency API, I find that the Windows App SDK dynamic dependency API is limited to non-packaged applications, and packaged applications will directly fail to call this function. Looking at the source code, we found that this is due to the fact that the WASDK's dynamic dependency API has actively restricted this, and we hope that the Windows App SDK team will remove this restriction and allow the packaged application to be called normally.

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

我的项目共同使用了 WinUI 2 和 WinUI 3，WinUI 2 和 WinUI 3 共同包含 Microsoft.UI.Xaml.dll 依赖库，需要使用 MSIX 动态依赖项 API 来解决这一冲突。当我使用 Windows App SDK 动态依赖项 API 时，发现 Windows App SDK 动态依赖项 API 仅限于非打包应用，打包应用调用该函数会直接失败。查看源代码发现，这是由于 WASDK 的动态依赖项 API 主动对此做出了限制，希望 Windows App SDK 团队能把这一限制去掉，允许打包应用程序正常调用。

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


https://github.com/microsoft/WindowsAppSDK/blob/aa9c8b8730ea23b656e882766839e090335e2f93/dev/DynamicDependency/API/MsixDynamicDependency.cpp#L36

https://github.com/microsoft/WindowsAppSDK/discussions/4819

The relevant entry point is dev/DynamicDependency/API/MsixDynamicDependency.cpp at line 36; start there to trace the packaged-app restriction. Read discussion #4819 for the expected behavior and constraints. Done means the Windows App SDK dynamic dependency API no longer rejects packaged applications for this scenario, with the packaged WinUI 2 and WinUI 3 use case covered.

Written by the indexing model from the issue text.