Install MSVC2017 for OpenJ9 windows compile machines

[jdekonin]

As per #1697 Windows will support compiling with VS2017 shortly once the changes are merged. VS2017 needs to be installed on the build machines and then used to build JDK11.

[ChengJin01]

@jdekonin, I believe some Ansible scripts https://github.com/AdoptOpenJDK/openjdk-infrastructure need to be updated to install VS2017. If so, I will get started to figure out how to get this work.

[ChengJin01]

I already created a change for VS2017 at https://github.com/ChengJin01/openjdk-infrastructure/tree/update_install_vs2017. @jdekonin is helping to verify whether it works via Ansible Tower.

[vsebe]

Installed MingWG-W64 8.1 and VS2017 on windows machines:

• win2012r2-x86-1
• win2012r2-x86-2
• win2012r2-x86-3
• win2012r2-x86-4

[vsebe]

To enable VS2017 see: #2792

[vsebe]

Playbook update for MinGW: adoptium/infrastructure#479

[vsebe]

JDK11 build
Failure: make[5]: *** [run_omrddrgen.mk:73: ../j9ddr.dat] Segmentation fault - know issue: eclipse-omr/omr#2885

[ChengJin01]

For the temporary solution, the crash can be avoided by specifying --enable-ddr=no to disable DDR-related code as DDR doesn't affect the operation of VM.
e.g.
bash configure --with-freemarker-jar=/cygdrive/c/openjdk/freemarker.jar --with-boot-jdk=/cygdrive/c/openjdk/jdk10 --with-toolchain-version=2017 --enable-ddr=no --disable-ccache`

[pshipton]

Note --enable-ddr=no is no longer required since eclipse-omr/omr#2944 was merged and promoted to openj9.

[pshipton]

Heads up that we are investigating using clang instead of mingw on Windows. If performance testing looks good we'll have to install clang on the builds machines as well.

[pshipton]

MSVC2017 is installed and in use for Java 11 builds.