Proper display / filtering of ROOT log messages from stderr in terminal output and InfoLogger

[ehellbar]

Applying the same logic for the terminal/GUI output and the InfoLogger.

For the terminal output, there is a new logLevel variable in the DeviceInfo which is initialized to the severity level of the device from the command line or to Info by default. This variable is independent of the DeviceControl::logLevel and it replaces the DeviceControl::logLevel to determine which logs are printed in the terminal. Like this, the DeviceControl::logLevel only sets the severity of the logs displayed in the GUI itself.

[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-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1

[ktf]

std::map is really for sorted lookups where you keep adding and removing from the map. Maybe you should use a std::unordered_map. In any case, please move it out of the header.

[ehellbar]

removed this map, used an if...else block instead like for the Fair logs.

[davidrohr]

Looks good. Just one question: What will happen with severity unknown? Will it be filtered, e.g. if we say --severity error, or will it be printed?

[ehellbar]

severity unknown is numerically bigger than fatal, so it will always be printed. And in the InfoLogger, it will be set to error, which is (and was) the default severity for stderr messages.