src: fix kill signal on Windows

[huseyinacacak-janea]

On Windows, where POSIX signals do not exist, the signal argument will be ignored, and the process will be killed forcefully and abruptly (similar to 'SIGKILL')

As stated in the documentation of Node.js, the signal parameter of child process kill function is ignored.

However, when we execute spawn(process.execPath, ['-v']).kill('SIGHUP');, it throws an exception with the code ENOSYS. This is not consistent with the documentation.

I've looked at the implementation in libuv and have seen that only four signal types are supported to kill a process on Windows.

This PR fixes this issue by changing the signal to SIGKILL if it differs from SIGQUIT, SIGTERM, SIGKILL, and SIGINT. In addition, there is a slight change in the documentation to clarify the signal parameter.

Fixes: #42923