- remove "void ExceptionHandlingDecorator::setDataValidity(DataValidity newValidity)"
- add "void ExceptionHandlingDecorator::setOwner(EntityOwner* owner)" and remove owner setting in constructor

- New flag parameter for ExceptionHandlingDecorator::genericTransfer.
  Method does not invalidate data if flag invalidateOnFailure is set to
  false.
- Write related methods in ExceptionHandlingDecorator set
  invalidateOnFailure flag to false

Changes resolve ticket #57.

- Exception handling decorator and ThreadedFanOut send condition variable notificatios via the DeviceModule
- FanOut sends terminate to impl and all slaves.
Solves (some?) shutdown issues, but breaks bi-directional array test.

Otherwise it is impossible to shut-down the server if the device could
not be opened at all or is in constant error state

Fixes #39

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.

 - Have a ZMQ push-type variable from a DOOCS-backed device that is NOT
   used as a trigger (otherwise the bug does not happen)
 - Connect that to an ScalarPushInput in an ApplicationModule
 - call readAnyGroup() from the ApplicationModule's main method

=> ReadAnyGroup.finalise() will cause an infinite recursion between
ExceptionHandlingDecorator::doReadTransferAsync and
TransferElement::readAsync because of wrong dispatching to the decorated
type

  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.