Windows CI machine updates

[joaocgreis]

@nodejs/build

I will change and rebuild some/most of the Windows machines we have connected to CI to add VS2019 to the matrix and better balance other versions for the current needs.

I will try to keep node-test-commit-windows-* working all the time, but expect jobs to queue for longer periods when the number of machines is reduced.

I will try to keep other jobs working as well, but please let me know if something is not working as expected.

[joaocgreis]

I'm planning to include the VS version in the host names, as metadata in the OS section (similar to arm_cross machines). This reinforces the restriction that only one VS version should be installed and makes the machines easier to manage, both because Ansible is made a bit simpler and we can know with a glace what version is installed.

Please let me know if there are any objections. (cc @rvagg)

[richardlau]

I will try to keep other jobs working as well, but please let me know if something is not working as expected.

@BethGriggs is seeing Windows CI failures on v10.x against releases that weren't seen at the time the releases were made (nodejs/node#30639 (comment)). Two Windows nodes have been marked offline in #2070.

[joaocgreis]

The new machines are in place and the Windows job has been updated. PR coming soon with build repo changes.

Resuming jobs before the change does not work, I expect this to be an issue in the next few days. I'll rebuild the jobs I see failing.

I've updated the libuv job, there are a few others that I still have to get to. Please let me know if there are issues in other jobs.

[joaocgreis]

Many compile jobs have failed in the last day. I noticed this happens after a V8 canary compile job runs, every compile job of the same type that runs after it fails. I'm still investigating.

For now, if you see a compile job failing with a lot of errors like

openssl.def : error LNK2001: unresolved external symbol ...

please take the machine that ran it offline.