MSIX packaging for arbitrary .NET project types

Nobody has claimed this yet.

### Motivation

The .NET SDK supports streamlined MSIX publishing for [WinUI 3](https://learn.microsoft.com/de-de/windows/apps/windows-app-sdk/single-project-msix?tabs=csharp) and [MAUI](https://learn.microsoft.com/en-us/dotnet/maui/windows/deployment/publish-cli?view=net-maui-9.0) projects. For other project types one can use an [application packaging project](https://learn.microsoft.com/de-de/windows/msix/desktop/desktop-to-uwp-packaging-dot-net). Packaging projects are cumbersome to use, more complicated to use than `dotnet` in CI pipeline and cannot pass MSBuild properties to child projects easily.

### Desired solution

I would like to have MSIX packaging tools for arbitrary .NET project types including Avalonia, WPF, WinForms, Console. It should be compatible with other features like single file executable, trimming and Native AOT.

### Additional context

I originally posted this issue at dotnet/sdk#45045. However, as @Sergio0694 pointed out, MSIX packaging functionality is already implemented in `Microsoft.Windows.SDK.BuildTools.MSIX` and could be extended to support other frameworks than WinUI 3 or MAUI. Unfortunately, I could not find the source code for that NuGet package and hope that I am not totally wrong by opening this issue here.

Start by examining the existing MSIX functionality in the Microsoft.Windows.SDK.BuildTools.MSIX NuGet package and how WinUI 3 and MAUI projects invoke it. Compare that path with application packaging projects and dotnet CI usage. Done means supporting arbitrary .NET project types, including Avalonia, WPF, WinForms, and console apps, alongside single-file, trimming, and Native AOT options.

Written by the indexing model from the issue text.