Disable linker warning LNK4104 when building native AOT libraries

[MichalStrehovsky]

link.exe hardcodes a list of magic symbol names that it thinks should not be generated into import library and emits warnings if they are.

We don't have a mechanism to set visibility of UnmanagedCallersOnly methods and I don't think we'd want to make a public API for that. But this means that users get a warning that is not particularly actionable. We could either replicate this magic list of symbol names into compiler and generate these as PRIVATE (but then how do people opt out if they don't actually want this as PRIVATE?), or we can just suppress the warning.

This PR suppresses the warning.

Cc @dotnet/ilc-contrib @Sergio0694

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

link.exe hardcodes a list of magic symbol names that it thinks should not be generated into import library and emits warnings if they are.

We don't have a mechanism to set visibility of UnmanagedCallersOnly methods and I don't think we'd want to make a public API for that. But this means that users get a warning that is not particularly actionable. We could either replicate this magic list of symbol names into compiler and generate these as PRIVATE (but then how do people opt out if they don't actually want this as PRIVATE?), or we can just suppress the warning.

This PR suppresses the warning.

Cc @dotnet/ilc-contrib @Sergio0694

Author:	MichalStrehovsky
Assignees:	-
Labels:	area-NativeAOT-coreclr
Milestone:	-

[Sergio0694]

Would it be worth it to add a comment here with some context, maybe a link to the original issue or something so people will be able to understand why this is here? This suppression seems a bit random and arbitrary otherwise, and I could imagine folks having no idea about the WinRT shenanigans being confused when looking at this 😅