Weird app size issue with metapackage

Nobody has claimed this yet.

### Describe the bug

When I use the WinUI package, I get a larger app than using the entire winappsdk.

### Steps to reproduce the bug

1. Create a new WinUI app using the project template.
2. Reference the latest 1.8exp2 metapackage ``
3. Compile and run the app, and notice the bin folder is about 244mb
4. Replace the package reference with the WinUI specific one ``
5. Repeat step 3, but notice the output is now 355mb, even though I'm referencing less.
6. Add the package ``
7. Repeat step 3, but notice the app output now is back down to 244mb. It seems like this package is somehow responsible for not deploying unnecessary stuff.

### Expected behavior

App should be smallest with only the WinUI package referenced.

### Screenshots

_No response_

### NuGet package version

Windows App SDK 1.8 Experimental 2: 1.8.250515001-experimental2

### Packaging type

Packaged (MSIX)

### Windows version

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

### IDE

Visual Studio 2022

### Additional context

_No response_

Reproduce the packaged MSIX app using the WinUI, Microsoft.WindowsAppSDK, and Microsoft.WindowsAppSDK.Packages references described in the issue, then compare the bin folder sizes. Start by checking how these package references affect deployment in the Windows App SDK project template. Done means the WinUI-only reference produces the smallest expected app output.

Written by the indexing model from the issue text.