Add support for High-Water Mark in HistogramSender and histserv_nofairmq + reduce logs

See commit messages

Tested locally both the processing binary and the histogram server, but only over 10 TS from run 2942

Did not find a way yet to change the frequency of histo updates emission due to the way the HistogramSender is integrated in the variouos QA chains:

• grep -rn "PrepareAndSendMsg" algo/
• has in mind to add a sending only every N TS and/or every time at least M seconds elapsed since last emission (similar to what was done in the FairMQ versions years ago to avoid an updates flood when working with multiple parallel chains all starting at the same time)

Redmine: Refs #3289

Also of interest to: @s.zharko @v.friese

algo/base/HistogramSender.h

@@ -20,11 +20,13 @@ namespace cbm::algo
 
   class HistogramSender {
    public:
-    HistogramSender(std::string_view address)
+    HistogramSender(std::string_view address, int32_t hwm = 1)
       : fHistComChan(address)
+      , fHistHighWaterMark(hwm)
       , fZmqContext(1)
       , fZmqSocket(fZmqContext, zmq::socket_type::push)
     {
+      fZmqSocket.set(zmq::sockopt::sndhwm, fHistHighWaterMark);  // High-Water Mark, max nb updates kept in out buffer
       fZmqSocket.connect(fHistComChan);  // This side "connects" to socket => Other side should have "bind"!!!!
     }
 
@@ -54,7 +56,8 @@ namespace cbm::algo
     }
 
    private:
-    std::string fHistComChan = "tcp://127.0.0.1:56800";
+    std::string fHistComChan   = "tcp://127.0.0.1:56800";
+    int32_t fHistHighWaterMark = 1;
     zmq::context_t fZmqContext;  ///< ZMQ context FIXME: should be only one context per binary!
     zmq::socket_t fZmqSocket;    ///< ZMQ socket to histogram server
   };