moved exception handling documentation into its own dox file and added documentation about DataValidity flag propagation

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.

allow using the TestFacility without the testable mode, which can be useful for some tests of the framework itself

TriggerFanOut must catch exceptions when reading from the TransferGroup, since this cannot be handled by the decorator

Martin Killenberg authored 5 years ago and Martin Christoph Hierholzer committed 5 years ago

Creation of fanOuts is based on externalTriggerImpl (=trigger consumer), not externalTriggerNode (=trigger feeder).
- Fixes connection network but not exception handling.
- Lots of debug output left in the code for further investigation.

- 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.

move ApplicationModule::appConfig() to ModuleImpl::appConfig() so it can also be used from ModuleGroup

add ConfigReader.h to ApplicationCore.h, as the ConfigReader is now more strongly integrated with ApplicationCore

Implemented first part of #17: A HierarchyModifier can now be specified instead of the eliminateHierarchy boolean flag. No new functionality is yet added.

- 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