feat: Adding signal and external error detection & output

[MelReyCG]

This PR is based on Amandine work on adding error YAML file in GEOS (PR #3828), and aims at adding a detection & management inside GEOS of 1. Error signals, 2. External errors from dependencies, in order to be able to manage & output them in the log & error YAML file.

Managing those external errors gives us the opportunity to:

• output error message & context reliably in the log, even if the stderr get lost or used for another reason,
• be sure to detect any kernel / system allocator errors and add the stack-trace of these errors,
• factorize them with external tools / scripts, thus highlighting which are the source rank(s) of the issue.
• also has the effect to prevent the stacktrace to be cut by other ranks message, which could previously happen on a signal.

Without the pipe redirection proposed here, we encounter a lot of errors without any stacktrace and too minimalist (and sometimes even no message at all, just a cut log) on many HPC platforms and on the CI. The branch has been tested to provide the lacking info on many issues on P4.

This work also gives us the opportunity to tag later each dependency message (system, LvArray, Hypre, ...) to quickly identify / filter issues source.

---

(Replaces #3722)

[paveltomin]

@rrsettgast @wrtobin @paveltomin I need a review, this work will be useful for further debugging tasks

i more or less understand what is done here but don't really understand how it works, sorry
seems very low-level, can you share some examples - situation before and after ?

[MelReyCG]

@paveltomin thanks for the feedback, I'll work on the code clarity!

[wrtobin]

My only note is we might prefer ExternalSignalHandler just for specificity/clarity vs our existing error handling mechanisms, but not a hard requirement.

[MelReyCG]

I would like to keep the name general as this component does not process only signals, but also any message from external code (as an exemple, VTK error / warning messages).
Some messages may appear as (non-crashing) error for now, but we will be able categorize them with this component (or a sub-component of it).
Thanks for the review