- 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

Updated to use the new ReadAnyGroup instead of the old readAny function. Some tests are still hanging or failing (mostly due to shutdown issues)

Renamed Application::testableModeThreadName() into Application::threadName(), since this will be used for other purposes as well.