Windows - updates for mswin builds

[MSP-Greg]

Updates for mswin builds, no 'bugs' involved. Commit info:

1. 'package.json and yarn.lock' - 'housekeeping'
2. 'Windows mswin - update addVCVARSEnv' - Currently the 'vcvars.bat' file's path was found via a switch/select/case statement that hard-coded the Actions windows image string. A PowerShell module (vssetup.powershell) is available for finding information about Visual Studio installs, and it is installed on all Actions Windows runners. Use the module so hard-coded image strings aren't needed.
3. 'Windows mswin - use ucrt64 tools instead of mingw64' - Many repos need bash commands, and also use build utilities like bison or ragel. Currently, mswin builds are using the mingw64 tools, switch to the ucrt64 tools.
4. 'Actions - add windows-2022 mswin job'

[MSP-Greg]

Original PR used a PowerShell module known as vssetup.powershell, which contains quite a bit of functionality. But, running it took anywhere from 14 to 20 sec in one run. Too long.

Windows images also contain a utility named vsWhere, which is a compiled exe. It takes around a second to run. Last commit uses it...

[eregon]

Looks great, thank you and sorry for the review delay

[MSP-Greg]

sorry for the review delay

No problem. OSS is just a part of our lives...

Do you have any opinion about whether we/I should build the mswin Ruby with OpenSSL 3.0? Microsoft's vcpkg 'system' has updated to 3.0 from 1.1. I've also got all the packages needed to build mswin in the MSP-Greg/setup-msys2-gcc release. Hence, it could be installed by setup-ruby just like the mingw and ucrt archive files.

I think I'm aware of most of the repos it would affect, and most already work with OpenSSL 3.0...

[eregon]

Do you have any opinion about whether we/I should build the mswin Ruby with OpenSSL 3.0?

I think all GitHub-hosted runners currently use openssl 1.1, not 3, so probably best to stick to 1.1 while it's the case (unless that's problematic for mswin).

[MSP-Greg]

GitHub has announced that Ubuntu 22.04 will be available as a preview image in the near future. I believe it uses OpenSSL 3.

I'm running it locally, and building/using Ruby master, even added gcc 12.

Also, the current release of Microsoft's vcpkg system 2022.04.12 builds OpenSSL 3, so sometime soon the Actions Windows runners would build an mswin package with 3.

[MSP-Greg]

One thing I haven't mentioned. mswin builds use a different set of packages than either mingw or ucrt. In the past, it was kind of a mishmash of sources. Now, microsoft/vcpkg has all the packages needed to build mswin (the bison and ragel utilities from MSYS2 work with mswin).

Just last month vcpkg updated OpenSSL from 1.1.1 to 3.0 (diff). So, a new installation of vcpkg builds OpenSSL 3.0.2. Packages from vcpkg can be 'exported', so I've also got an archive file of all the packages needed to build mswin.

[eregon]

Sounds good. Yeah then it sound like using vcpkg packages is the best for mswin.