Add CI for Windows MSVC2019, MSVC2022, and SDE 32/64-bit

[samuel40791765]

Issues:

Resolves CryptoAlg-2094

Description of changes:

• This creates a CI dimension for Windows 32 and 64 bit SDE. Windows scripts were refactored to be more generic as well.
• We test with the Windows SDE with the MSVC2019 build.
• SHA256 dispatch test fails for some reason on the Debug build with newer processors when building for 32-bit. Our digest tests still pass though, so it could just be some wrong assumptions. I've punted CryptoAlg-2137 to investigate.
• I also discovered how to properly build with MSVC2019 and MSVC2022 while working on this, so I added CI for the two compilers as well.
• Tested all dimensions against appropriate instance sizes.
  • SDE tests take 90ish minutes to finish on 32 cores. We try to fit our CI within 1 hour, so I went with the next largest instance.
  • Github provided Windows instances only have 2 cores and aren't sufficient enough for our regular Windows tests. The next larger instance was 8 cores, so I went with that.

Call-outs:

Unsure how slow the Windows SDE tests will be in Codebuild.

Testing:

New CI dimension

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

[samuel40791765]

Tests are slow and insufficient memory on the instance causes the tests to fail in Codebuild.. A single test run takes nearly 2 hours on the beefiest instance too.

[ RUN      ] BIOTest.Gets
[       OK ] BIOTest.Gets (364 ms)
[ RUN      ] BIOTest.InvokeConnectCallback
new[] failed to allocate 131072 bytes
crypto/crypto_test (for CPU "bdw")
crypto/crypto_test failed to complete: exit status 0xffffffff

For a better picture, it took me 50ish minutes to finish one run on a z1d.metal instance I spun up.