Missing digital signatures on Windows native dependencies #20489
Description
Describe the bug
On Windows, if Native AOT publishing an app, there are 3 DLL dependencies.
av_libglesv2.dll
libSkiaSharp.dll
libHarfBuzzSharp.dll
I notice that none of these 3 DLLs are digitally signed. In the past, Windows has never really enforced DLL signing, however we've gotten reports from some users that Smart App Control (https://learn.microsoft.com/en-us/windows/apps/develop/smart-app-control/overview) is blocking some users due to missing code signing on the DLLs (We sign the output executable).
I can sign these 3 DLLs myself, however that's not an ideal solution, and I feel like whoever publishes those artifacts should be signing them. I also have also some qualms about signing a DLL I didn't produce the build for, although I have to do that already on macOS, so maybe not as big of a deal. It looks like at least av_libglesv2 comes from Avalonia.
To Reproduce
Native AOT publish any app. See the DLLs are not signed, even though they were not built as part of the build.
Expected behavior
Any required Avalonia native binaries are signed.
Avalonia version
11.3.9
OS
Windows
Additional context
No response