Fix/robot unit streaming

described in https://git.h2t.iar.kit.edu/orga/software-organization/-/issues/258

Changes:

• RobotUnit: new property RTLogging_LogAllMessages=false to only log newest message with the defined rate of the logging thread (usually 50-100Hz). If the computation takes too long, then the queue will be filled and the data in the RobotStateMemory will be outdated (sometimes even ~1 second!). By default, RTLogging_LogAllMessages such that this change is opt-in.
• RobotStateMemory: using triple buffer for communication between robot unit reader (retrieves data from robot unit) and writer (commits data into memory)

source/RobotAPI/components/units/RobotUnit/RobotUnitModules/RobotUnitModuleLogging.cpp

@@ -389,6 +389,8 @@ namespace armarx::RobotUnitModule
         DataStreamingEntry& streamingEntry = rtDataStreamingEntry[receiver];
         getProperty(streamingEntry.rtStreamMaxClientErrors,
                     "RTLogging_StreamingDataMaxClientConnectionFailures");
+        
+        getProperty(logAllEntries, "RTLogging_LogAllMessages");
 
         ARMARX_INFO << "start data streaming to " << receiver->ice_getIdentity().name
                     << ". Values: " << config.loggingNames;
@@ -879,8 +881,6 @@ namespace armarx::RobotUnitModule
         rtLoggingBacklogRetentionTime =
             IceUtil::Time::milliSeconds(getProperty<std::size_t>("RTLogging_KeepIterationsForMs"));
         
-        logAllEntries = getProperty<bool>("RTLogging_LogAllMessages");
-
         ARMARX_CHECK_GREATER(getControlThreadTargetPeriod().toMicroSeconds(), 0);
     }