The previous implementation using the mutex had two issues:

1. The mutex was locked in a different thread than unlocked (DeviceModule constructor vs. handleException() thread). This results in undefined behaviour.
2. The boost::shared_mutex::lock_shared() function is not an interruption point, so applications did not terminate while waiting for initial values. (boost::latch::wait() is an interruption point.)

Just use enableDebugDataLoss() to enable debug output.

fix tsan complaining about incrementing/decrementing testableMode_deviceInitialisationCounter outside testable mode

- All variables conceptually have an initial value now.
- All initial values read by blocking read() before starting the main loop.
- More tests failing, probably to old test exceptiations and wrong test implementations.

- tests still failing
- modifications incomplete
- cleanup needed

- Initial values are sometimetimes only propagated in the first run of the main loops, not in prepare. If other modules are waiting for it they cannot enter their main loop. That's why all threads have to be started first, and only the it is waited for all of them to enter testable mode.

TriggerFanOut is waiting for the device to open before starting the main loop to avoid logic_error in TransferGroup::read()

- activated some tests which were commented out in testPropagateDataFaultFlag
- data validity propagation still failing. Only the data content is working until now.

- Removed extra exception handling from TriggerFanOut. It is all done by the ExceptionHandlingDecorator
- ExceptionHandlingDecorator does not drop out of testable mode until the device is initialised.

- Removed extra exception handling from TriggerFanOut. It is all done by the ExceptionHandlingDecorator
- ExceptionHandlingDecorator does not drop out of testable mode until the device is initialised.

- removed DeviceModule::waitForRecovery()
- ExceptionHandlingDecorator is throwing to skip transfers

Ongoing refactoring. Consuming fanout works again.

	-waitting for recovery is now outsourced in function
	DeviceModule::waitForRecovery()

	-everywhere where the function is called, the new function is now called.

Need to wait until the internal fan out threads have been launched and acquired the testable mode lock before continuing with app starting and testing to avoid race conditions.

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

Fixes #39

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

- implement ThreadedFanOut version with return channel
- add test for ThreadedFanOut with return channel