LogicalName and ManifestResourceName are not respected #10
Description
MSBuild <EmbeddedResource> items can have LogicalName or ManifestResourceName specified, which affects the internal resource stream name. See https://learn.microsoft.com/en-us/dotnet/core/resources/manifest-file-names
I'd have to do more experimentation on which use cases this is used for, but I have several projects using LogicalName currently and ran into this trying to switch to this source generator instead of the VS generator.
Funny enough MS actually broke the VS generator's support for LogicalName but with the VS generator you can always just update the generated code so it's not a blocker. For this source generator the code can't be modified so it's more important to get it right.