* Use templated version to add a trigger.

A trigger is needed for Poll type inputs. Still it can not be used for
Devices. Here one has to call addSource manually.

* No need to use a trigger. Fix connections by moving all to history.

Trigger is only needed for DeviceModules. So in case of device addSource
still needs to be used, because no tags are present for devices.

* Add option to specify the directory where history will appear in CS.

* Remove CS tag not needed any more.

* Update documentation.

* Update documentation of logging module.

* Remove CS tag not needed any more.

* Remove parameter not needed. AddSource for ConnectingDeviceModule. Docu.

* Create test case for testing multiple modules having the same.

* Use message IDs to support modules with similar names.

ToDo: Remove variable connections to CS like with MicroDAQ.

* Use automatic connection via CS. Rebuild hierarchy in Logging module.

* Put logging variables into a separate hierarchy level.

* Let user write to alias via CS. Keep last message in the PV.

Before the message was always cleared after writing it. Now a new log
level is used to indicate the situation that write was called on the
message PV without calling sendMessage - it happens if the owning module
calls writeAll(). Now the last message of each sender is availble in the
CS.

* Add test with modified hierarchy.

* Clang formaat applied.

* Hide internal PVs. Use different internal tag to work with regex.

* Fix initial msg. Add automatic connection to the LoggingModule.

Now the Logger is a VariableGroup and in the prepare() method an empty
msg is written once. This makes sure the LoggingModule is not waiting
for initial values of Loggers and messages by other Loggers get lost.

* Add message in case on modules with Logger are found.

* Fix test and remove implementation of removed method.

* Do not use hard coded tags but use default tags.

Now all tags given to the LoggingModule are used to look for senders.

The user can now also choose to publish messages only to the control
system.

I observed that, after reading the message sometimes the log level was
wrong. Most likely because it was updated after the message was read.
Now the log level is bound to the message. This also reduces the number
ctk variables.

Fix missing object name in the example.

It is suffiecient to have the message being push type.
readAny of the ReadAnyGroup will update poll type variable
automatical once there was an update of the push type message.

Some custom tags from private servers have been removed.
Added "CS" tag, which allows to use findTag on the Logging module
and connect it directly to the control system.

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.