build,win: make installer res files ready for translation

[refack]

Fixes: #819

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[nodejs-github-bot]

@refack build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1536/pipeline

[refack]

We just added a bunch of strings, they need translation.
BTW: I have no idea the winproj change works, and what is the output (multiple file, or one multicultural file).

/CC @nodejs/i18n @fhemberger

[fhemberger]

@nodejs/i18n Could we hook up the installer files to the same translation process as the docs?

[fhemberger]

Or the more general question would be: Do we want a translated installer at all?

The initial translation efforts are almost four years old, IIRC the Mac version never landed at all. It was such a long and tedious process with several PR revisions, also a lack of feedback from folks who worked on the initial installers. In the end I lost track and it discouraged me from contributing further.

Now seeing that the changes which were supposed to land after $ImportantRelease never made it in at all, I don't know …

[refack]

Or the more general question would be: Do we want a translated installer at all?

Very valid question! If we don't have an i18n support team, this will break. Also AFAIK the current repertoire of translations is indicative of the Collaborators not of the users (no Spanish, Portugese, Hindi or Bengali)

[Trott]

@nodejs/community-committee Any chance you can help get translations here?