Creating a singleExe from UnPackaged app breaks the latest WindowsApp SDK

### Describe the bug

Currently using the latest SDK 1.5.240428000, it fails to generate the `resource.pri` when creating the SingleExe. I think, it is breaking the latest SDK behavior.

If we use the SDK version 1.4.240211001, It creates the SingleExe properly with all dependency files.

It's replicate in the CustomControl library project also.

### Steps to reproduce the bug

[CustomControl.zip](https://github.com/microsoft/WindowsAppSDK/files/15219997/CustomControl.zip)
[SimpleApp.zip](https://github.com/microsoft/WindowsAppSDK/files/15220007/SimpleApp.zip)

1. Open the SimpleApp project.
2. Tools->Commands->Developer Powershell. Use below command line for creating the SingleExe.
` dotnet publish SimpleApp.sln -c Release -p:Platform=x64 -p:PublishSingleFile=true --self-contained true -p:WindowsAppSDKSelfContained=true`
3. Now, open the Bin folder and check the exe.

Note: Exe will not launch in launch SDK.

### Expected behavior

It should launch the exe properly as like windows SDK (1.4.240211001).

### Screenshots

In Version `1.4.240211001`


In Version `1.5.240428000`


### NuGet package version

Windows App SDK 1.5.3: 1.5.240428000

### Packaging type

Unpackaged

### Windows version

Windows 11 version 22H2 (22621, 2022 Update)

### IDE

Visual Studio 2022

### Additional context

_No response_

Start with the attached SimpleApp project and reproduce the failure using the published dotnet command, then compare SDK 1.5.240428000 with 1.4.240211001. Check the generated Bin output and the resource.pri file; this is done when the unpackaged SingleExe launches successfully with its dependency files under the latest SDK.

Written by the indexing model from the issue text.