Removing EnableMsixTooling from project file for unpackaged applications produces crashing published app

Describe the bug

From my observations EnableMsixTooling is responsible for renaming the pri file from [ProjectName].pri to resources.pri. If EnableMsixTooling is ommited because it is not needed for unpackaged applictations and such an application is then published from the Visual Studio wizard, the [ProjectName].pri file is not copied to the publish directory.

Steps to reproduce the bug

1. Create a new application
2. Set <WindowsPackageType>None</WindowsPackageType>
3. Remove EnableMsixTooling
4. Publish the application with the Visual Studio wizard

Expected behavior

The pri-resource-file should be copied in every possible case, as not copying it produces a non runnable crashing output.

Screenshots

No response

NuGet package version

Windows App SDK 1.3.2: 1.3.230602002

Packaging type

Unpackaged

Windows version

Windows 10 version 22H2 (19045, 2022 Update)

IDE

Visual Studio 2022

Additional context

No response

Reproduce the unpackaged application flow with None and without EnableMsixTooling, then publish it through the Visual Studio wizard and inspect the output. Trace how the project file handles the [ProjectName].pri resource and compare the result when EnableMsixTooling is present; done means the PRI file is copied and the published app runs.