- fixed bug that there was a nullptr exception handler in the list with default value from constructor (caused all ApplicationCore to fail)

first implementation of device initialisation handler. Simple test passes, but needs to be extended.

implemented first interface change in DeviceModule to support initialisationHandlers. Test in place but failing due to missing implementation.

changed: device is not intialized in constructor anymore.

Test still does not work.
-Unable to get the exception status for the device throwing exception.
-Second device only works it has it's own trigger.

According to ChimeraTK/DeviceAccess#61 Devices will no longer close on their own (e.g. when throwing an exception). The exception handling now takes into account that the device always stays open

- add test for full exception handling

  DeviceModule and ControlSystemModule now do not take the optional prefix argument in their constructors any more. Use the [] operator instead to get the submodule.

- Add ExceptionHandlingDecorator and decorate all device variables with it.

- added more comments
- need to catch exception by reference, else the message seems to be lost
- test if the message is correct
- test if device is really closed and opened again
- changed names of status variables in control system to match the general naming conventions

Added preliminary support for bidirectional variables. There are still some known issues, e.g. concurrent updates can still lead to race conditions. This will be addressed soon.

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.

Fixed wrongly created hierarchies when directly connecting a device to the controlsystem using connectTo(). Now proper virtual submodules are created for each hierarchy level, insted of keeping the slash in the variable name.

fixed connectTo() for direct device to control system connections when using the [] operator on the device module

fixed connectTo() so it now uses the dynamic/virtual model and thus obeys e.g. eliminated hierarchies etc.

Fixed some more problems with the move sematics of EntityOwner/Module. Re-registration at the owner was missing and some things were done in the wrong place. Also the move assignment is now back again.

put the move constructor and move assignment-operator into the EntitiOwner base-class and inherit them

also make sure for DeviceModules to always return the same sub-module with the [] operator when passing the same sub-module name

Instead of making the DeviceModule return the same VariableNetworkNode for the same register, an optimisation step before realising the connections (but after all connections have been defined) is performed. In this step, all networks sharing the same (device-type) feeder will be merged. This is more flexible and avoids problems with (potentially different) triggers etc.