Deploy will not copy dlls that vcpkg generates if you don't edit code related to cpp

Nobody has claimed this yet.

### Describe the bug

The common situation is that you only modify xaml page code, which won't trigger user code compilation.

### Steps to reproduce the bug

A winui C++ project.
Enable vcpkg integration.
Use manifest mode.
Add a port.
Start debugging. (or directly trigger deploy by right click the project and deploy)
Stop debugging and modify a xaml file.
Begin debug or deploy.
It will show a dll missing dialog. Because the dlls didn't copy to the AppX folder in the output directory.

### Expected behavior

_No response_

### Screenshots

_No response_

### NuGet package version

1.8.260317003

### Packaging type

Packaged (MSIX)

### Windows version

Insider Build (xxxxx)

### IDE

_No response_

### Additional context

VS 2026
You can directly use my repository to reproduce.
https://github.com/hoshiizumiya/opennet

Start by reproducing the issue with the linked opennet repository: use a packaged WinUI C++ project with vcpkg manifest mode, deploy once, modify only a XAML file, and deploy again. Investigate the deployment behavior after XAML-only changes. Done means vcpkg-generated DLLs are copied into the AppX output directory and debugging or deployment no longer shows a missing-DLL dialog.

Written by the indexing model from the issue text.