Unfortunatly this currently breaks the ServerHistory module, as it relies on slashes in accessor names. The MicroDAQ module had the same issue but has already been fixed. This fix can be adopted to the ServerHistory module as well.

Now one can add ScalarOutput and ArrayOutput variables to the history modules by using tags.

This is still not nice. Now for every data type an individual module needs to be created.

Do not rely on EntityOwner for accessig Application object.

- renamed timeout to period.
- introduced PeriodicTrigger::sendTrigger
- mainloop logic bypassed on startup if owner application is in testable
  mode.

- Timeout is now in milliseconds to allow more flexibility
- Default timout can be specified in the constructor
- Make sure the time interval is perfectly matched by using sleep_until instead of sleep_for

- Make data decimation configurable
- Addded some documentation
- Some code cleaning (eliminate warnings, move internal classes into detail namespace)

If sendMessage is used before chimeraTK process variables are initialized an internal buffer is used to store those
messages. Once the process variables are initialized the messages from the buffer are send.

Include descriptions of the owning Module in the descriptions of each process variable to make them more complete.

Updated to use the new ReadAnyGroup instead of the old readAny function. Some tests are still hanging or failing (mostly due to shutdown issues)

- Added tag "MicroDAQ.CONFIG" to all configuration variables, to make it easier to publish only them into the control system

changed again the interface of SplitArray: the number of groups and elements per group don't have to be a template parameter, instead they are now specified in the constructor

ConfigReader: make exception what() message more elaborate when not finding a variable in the config file in get()

Extended the SplitArray modules to also allow splitting into multiple arrays of the same size. This breaks the interface of the old modules, but they were not yet used anywhere so this should be ok.

configuration variables are now provided to the receivers right away without any read(). Updates will never be sent.

allow obtaining the config values already before connections have been made through a speicial get() function