Promoting operational errors to critical severity

[ehellbar]

This PR promotes Error messages which require some action from the shifter to the InfoLogger Ops level.

As a first step, "(core dumped)" messages are set to severity=Error and level=1 in the EPNstderrMonitor task. I will also check for other stderr messages which we might want to promote.

Now, in the second step, we should promote known DPL Erros (https://alice-qc-shifter.docs.cern.ch/pdp/infologgerMessages/ and https://alice-operations.docs.cern.ch/ECS/ECS_operational/#known-messages-in-the-guis) for which we ask the shifter to act (create BKE or call an expert) to level=1.

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1

[davidrohr]

Ok, but why did we remove info in and print in?

[ehellbar]

They will be anyway filtered before by mFilters.