Consider optionally setting up a signal handler that reports stack buffer overruns more nicely

The Rust runtime sets up a signal handler which enables it to produce a nicer message when a stack overflows, however this only works when the guard pages set up by the Rust standard library itself are hit. That is, for the main stack and for the stack of the threads created std::thread.

There may be value in stacker setting up a similar signal handler(s) for the guard pages it sets up by itself, but the functionality likely wants to be made optional (in order to reduce the cost of allocating/deallocating a stack region)

Start by reading the linked Rust runtime implementation in library/std/src/sys/unix/stack_overflow.rs, then trace how stacker creates and frees its own guard-page-backed stacks. Determine which signal handler behavior is needed and where an optional configuration should live. Done means stack overrun reporting works for stacker-managed stacks without imposing the cost when disabled.