Re-enable tests for ELF enclave on Windows

[CodeMonkeyLeet]

Prior to PR #632, many more tests were enabled for running ELF enclaves on Windows. This issue tracks re-enabling these tests and fixing any new build breaks and issues introduced into them while they were disabled:

• abortStatus
• create-rapid
• ecall_ocall
• echo
• enclaveparam
• cppException
• getenclave
• hostcalls
• hexdump
• initializers
• libc
• libcxx
• libcxxrt
• memory
• mixed_c_cpp
• ocall
• ocall-create
• print
• report
• SampleApp
• SampleAppCRT
• sealKey
• stdcxx
• thread
• threadcxx

In addition, we should also evaluate enabling tests that were previously not enabled due to a dependency on oegen which has since been replaced by oeedger8r that has been enabled to run on Windows by PR #895:

• file
• pingpong
• pingpong-shared

[anitagov]

Enabled 16 ELF enclaves on Windows with my PR #1173

[anitagov]

Enabled 6 more tests with PR #1217

[anitagov]

Enabled 2 more tests (cppException and sealKey) with PR #1280

[anitagov]

PR #1289 - Enabled abortStatus for Windows after resizing ELF enclave and bypassing the result from terminate_enclave.

[anitagov]

Please look at my issue #1008 for tests that have been enabled. I am also updating this issue to keep in synch.

[anitagov]

Enabled mbed tests for Windows with my PR #1372 .
Disabled ecall_ocall for Windows as it intermittently fails with my PR #1415 .

[anitagov]

The current list of tests that are not enabled on Windows are:
create-rapid
crypto_crls_cert_chains
ecall_ocall - Was enabled and recently pulled out due to size issues on Windows
libcxx
libcxxrt
libunwind
memory
qeidentity - Attestation is not supported on Windows yet
report - Attestation is not supported on Windows yet

[anitagov]

libc tests were enabled on Windows with PR #1508

[CodeMonkeyLeet]

Closing this as outdated and tracking remaining tests as part of parent epic #39 directly.