Update submodules

[waahm7]

Description of changes:

• update to latest submodules
• Here it is announced that dotnet 5.0 will be removed on 29th Jan. Add a setup dotnet action for 64bit Windows.
• For 32 bit windows, we disabled the tests at link. Disable it in builder.json as well. We can enable it after setup dotnet action supports installing 32 bit .net. There is a PR in progress for that.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[graebm]

not your fault, but

ilammy/msvc-dev-cmd <-- in my experience, this github action has no effect

it ended up in all our ci.yml files when we were first setting up our repos and copy/pasting everything

later we discovered it had no effect, but we've never made a concerted effort to fix this across our 20+ repos :(

[waahm7]

https://tenor.com/en-GB/view/coding-programming-pink-panther-when-you-delete-a-block-of-code-that-you-though-was-useless-gif-17338075

[graebm]

not your fault, but this "windows-vc14" run isn't doing what it claims.

vc14 means version 14.0 of the compiler, aka toolset 140, which came with Visual Studio 2015, but you can still use those older toolset versions with later versions of Visual Studio

but it's actually just using the default compiler on this machine, which is Visual Studio 2019's version 14.29

Here's the line in the logs where you see what it's actually using.

-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x86/cl.exe

and then you cross-reference that against the Wikipedia page that details what the hell those version numbers mean. And you see that 14.29 means it's the latest build Visual Studio 2019 compiler

[waahm7]

Added a TODO for now.