Fix non-merged epoch handling in BMon and TOF online unpackers

=> It was properly implemented in legacy unpackers but the if condition got lost during the porting by Dominik
=> For now we just count them as errors, no further treatment done (in legacy unpacker it was a debug2 log message).

Putting myself as reviewer as this is kind of urgent to fix and I checked locally that the problem is gone (with some custom log messages in my local version before making the commit)

Of interest to @v.friese @a.toia @d.ramirez @n.herrmann

Redmine: Refs #3461

algo/detectors/bmon/UnpackMS.cxx

@@ -89,7 +89,14 @@ namespace cbm::algo::bmon
           break;
         }
         case critof001::MSG_EPOCH: {
-          ProcessEpochMessage(message[messageNr], time);
+          if (critof001::kuChipIdMergedEpoch == message[messageNr].getGet4Idx()) {
+            ProcessEpochMessage(message[messageNr], time);
+          }  // if this epoch message is a merged one valid for all chips
+          else {
+            /// FIXME: Should be checked in/forwarded to <some> monitor <task?>, here we just jump it
+            std::get<1>(result).fNumErrInvalidAsicEpochs++;
+            continue;
+          }  // if single chip epoch message
           break;
         }
         case critof001::MSG_SLOWC: {