Bump FairLogger to v2.1.0 and InfoLogger to v2.8.2

[ehellbar]

Introducing a "critical" log message severity, required to distinguish critical errors for shifter operation.

[ktf]

It looks like there is a genuine incompatibility between InfoLogger and the new FairLogger.

[ehellbar]

ok, I will check if it is only these two string_views or if there is more

[ktf]

Keep also in mind that c_str() is guaranteed to be 0 terminated, string_view is not.

[ehellbar]

waiting for AliceO2Group/InfoLogger#95 to also bump InfoLogger here

[sy-c]

My bad, I messed up with the include file during the test... Will fix shortly

[sy-c]

I fixed infologger and pushed v2.8.2

The include issue escaped my attention as I did the release integration tests using InfoLogger instead of libInfoLogger (which is the one included by the O2 components).

[ehellbar]

the compiler on macOS throws a warning when using enums in switch statements (in this case fair::Severity) and not handling all of the enumerators, which is the case here (missing the case for the new critical severity introduced with this bump of FairLogger). For PR checks, we use -Werror so we get an error here. Locally on my mac, the latest O2@dev with this alidist compiles successfully, throwing only the warning.

The O2 PR to fix this is already open but needs the bump of FairLogger first: AliceO2Group/AliceO2#13957

[ehellbar]

ping @ktf