fix for recording with LTM when dealing with broken "sent"-timestamps, like in Proprioception of RobotState Memory.
In this case the frequency filter takes the "arrived" timestamp, as this is normally not broken.

tested in Simulation (also with multiple GUI instances)

tested in simulation

Tested in Simulation

- we do not need all memories to be visible on every GUI, reduces unnecessary queries to the memory servers

Add a common base class for both HolonomicPlatformVelocity controllers
and add a property with which to choose one.
Make the acceleration limits also configurable via properties.

simplifying robot state and virtual robot reader: only robot name is required as input parameter instead of robot description