The default value was properly propagated but not visible to the test until a value was sent through the return channel.

This can be overridden by a newly introduced boolean argument. Including the return channel was causing problems e.g. when propagating the DataValidity flag.

- Exception handling decorator does not allow to leave testable mode before
  devices are up
- Test facility makes sure that testable mode counter is zero at the end of startApplication()

wip #47: register accessor for write after open in DeviceModule if write cannot be performed in initialisation phase

change declaration of 'decrementDataFaultCounter' in 'EntityOwner' to take a bool parameter and adjust rest of the code to it
implement 'decrementDataFaultCounter' in 'ApplicationModule' according to ticket #95 -> rewrite all outputs when 'faultCounter' goes from 1 to 0

remove commented part of ExceptionHandlingDecorator - 'void doPreRead() override' and its implementation

removed doPreRead() / doPreWrite() , doPostRead() / doPostWrite() from ExceptionHandlingDecorator - tests are now failing

	Ticket #79
	- documentation for addRecoveryAccessor() and getRecoverySharedMutex()

do not read initial values in TestFacility if testable mode is disabled, as this is subject to race conditions then

  - Cleaned up comments
  - Place using-declaration of buffer_2D to class definition so the base
    class name can be omitted in the implementation

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.