Revise tools scripts to be python3 compatible on win32 and enable github ci for win32

[lygstate]

We introduce setup_stdio function to setup stdout/stderr properly.
For python <-> python pipe, we always use 'utf8'/'ignore' encoding for not lost
characters.
For tty <-> python, we using native encoding with xmlcharrefreplace to encode, to
preserve maximal information.
For python <-> native program, we use naive encoding with 'ignore' to not cause error

update_exclude_list with binary mode so that on win32 would not generate \r\n

run-test-suite.py: Handling skiplist properly on win32

Fixes #4854

Fixes test262-harness.py complain cannot use a string pattern on a bytes-like object with running test262 with python3

For reading/writing to file, we use 'utf8' /'ignore' encoding for not lost characters.
For decoding from process stdout, using native encoding with decoding error ignored for not lost data.
Execute commands also ignore errors
Fixes #4853

Fixes running test262-esnext failed with installed python3.9 on win32 with space in path
Fixes #4852

support both / \ in --test262-test-list arg

On win32.
python tools/run-tests.py --test262-es2015=update --test262-test-list=built-ins/decodeURI/
python tools/run-tests.py --test262-es2015=update --test262-test-list=built-ins\decodeURI
should be both valid,
currently only --test262-test-list=built-ins\decodeURI\ are valid.

Support snapshot-tests-skiplist.txt on win32 by use os.path.normpath

Guard run-tests.py with timer.

All run-tests.py are finished in 30 minutes in normal situation.
May increase the timeout future.

wait JERRY_CHECK_TIMEOUT

Move Windows CI to github actions

Convert run-debugger-test.sh to run-debugger-test.py

After this change, run-debugger-test.py could running on Win32 and OSX

Define TERM colors for win32 properly

flush stderr.write stdout.write

On CI, the stderr are redirect to stdout, and if we don't flush stderr and stdout,
The output from stderr/stdout would out of sync.

Testing new Date(-8640000000000000) and fixes date for win32
So that the CI can passed

Fixes compiling warnings/errors for mingw/gcc

Fixes: #5107

CI for mingw also setup at the same time

JerryScript-DCO-1.0-Signed-off-by: Yonggang Luo luoyonggang@gmail.com

@robertsipka @LaszloLango

Currently there is no full CI for windows, and the Date is not implement valid win32,
by enabling the Windows ci for catching those

[LaszloLango]

Thank you, great PR in general. Just a few comments and questions from my side.

[lygstate]

@LaszloLango ready for take a look again

[lygstate]

rebased

[lygstate]

@LaszloLango errors="ignore" For python <-> native program, we use default encoding with error='ignore' to not lost data

This is for win32, for linux, no data will lost
as the native encoding is gbk and not every utf8 character will be print into it, and python failure will cause test failure that misleading

[lygstate]

@LaszloLango ping for take a look, I'd like it's merged before Release 3.0.0

[LaszloLango]

@lygstate, Can we move out the valgrind update to a separate PR? Is it necessary in this patch? What valgrind version are you updating? Did you do any modification in those headers beyond the update? Are there any manual changes in them?

[lygstate]

@lygstate, Can we move out the valgrind update to a separate PR? Is it necessary in this patch? What valgrind version are you updating? Did you do any modification in those headers beyond the update? Are there any manual changes in them?

OK, only affect mingw CI, let's me drop it first, done

[zherczeg]

LGTM