Improve stacktrace output during release_assert

[wezrule]

During a stress test @Srayman's node crashed, it hit a release_assert in pending_put but no other useful information was given. The abort signal handler is hit but no stacktraces generated.

From:
https://www.boost.org/doc/libs/1_67_0/doc/html/stacktrace/getting_started.html#stacktrace.getting_started.handle_terminates_aborts_and_seg

Not all the platforms provide means for even getting stacktrace in async signal safe way. No stack trace will be saved on such platforms.

Windows is one of these platforms, and while we cannot create the stacktrace dump during an unexpected crash (in the signal handler) we can output the stacktrace to a file before we abort ourselves in release_assert which will help in these cases.

All platforms will also now output the stacktrace to cerr.

Also moved linux specific code for crash dumps to the platform specific directory.

Tested on Ubuntu/Windows