Test Details Overview

Interrupt systest nodes with a console Ctrl+C on Windows and fix the other Windows systest failures (#5279)

* Interrupt systest nodes with a console Ctrl+C on Windows

A non-interactive bash starts background commands with SIGINT ignored.
On Linux and macOS the node replaces that with its own handler, but on
Windows the ignore sits in Git Bash's stand-in for the native process,
which drops the signal. daemon_interrupt and
ledger_extended_index_daemon waited out their timeout there and left
their nodes running until the job ended.

`interrupt_process ()` sends SIGINT through Git Bash's `kill -f` on
Windows, which delivers it to the native process as a console Ctrl+C.

* Time out the System Tests steps after 30 minutes

A hung systest step fails with its log kept instead of running until
the job's own timeout.

* Check the runtime files systest against the Windows PID and without nc

On Windows the PID file holds the PID Windows knows the node by, while
`$!` in Git Bash is the MSYS one, and Git Bash has no nc for the peering
port probe. `native_pid ()` maps the PID through /proc/<pid>/winpid and
the probe opens bash's /dev/tcp instead.

* Skip the RPC child termination systest on Windows

Windows delivers no SIGTERM to a console program, and the Ctrl+C Git
Bash sends in its place reaches the RPC child as well, which then exits
on its own instead of being terminated by the node.

__________

Type: commit

Hash: ccc864d80e5a9f3f86788e0c7e47948b7d1f4b63

Created: today

__________

gr0v1ty/nano-node:ccc864d80e5a9f3f86788e0c7e47948b7d1f4b63