Expose MSBuild property for Win32 VarFileInfo/Translation metadata

### Is your feature request related to a problem? Please describe.
I am trying to export a .NET app with only one supported language.
It seems like there's no way, without using a separate ``, to set `VarFileInfo/Translation`.
The user can see this by opening the properties of the executable in File Explorer and viewing the Properties.

This means that all exports, unless using the `` property, have a 'Language' of 'Language Neutral'.

### Describe the solution you'd like
An MSBuild property like ``:
e.g. `0x409, 1200`
...which would show as English (United States) in the Properties.
Or something less specific:
e.g. `en-US`
...which would automatically map to `0x409`, with some default codepage.

### Additional context
``, ``, ``, ``, `` and `` are all already mapped to existing Windows properties automatically.
While it is specific to Win32 metadata, this is one of the few fields exposed to the user that you still need to use a custom Win32 Resource File for.