- fixed that ConsumingFanOut is propagating the data to the slaves in case of exceptions
- /testPropagateDataFaultFlag currently passing (still commented sections)

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

  - Started reordering test sequence
  - Clean up read modes

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

Adapt test sequence of testDataFlowOnDeviceException to new spec.

Apapt test sequences of testDeviceReadFailure and
testDataValidPropagationOnException according to new data validity and
exception handling specifications.

Also fixes data race on runApplication in the constructor of
data_validity_propagation_noTestFacility test suite.

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

testAppModuleConnections uses BOOST_CHECK_EUQAL instead of BOOST_CHECK at some places for easier debugging

Throws logic_error if these modifiers are used in the top level

Currently does not get the modules in a way that they can be downcasted
to test if StatusMonitor, etc

  - Test use of illegal modifiers on top level in findTag()
  - Test getVirtualQualifiedName()

Initially, devices are closed and hence there is an error message. It goes away shortly when the device got opened. The new behavior is according to specification.

allows to control whether to wait for device recoveries in stepApplication

- The direction cannot be determined from the accessor which is being decorated
- Fixed wrong usage of feeding/consuming in Applicaton::createDeviceVariable. Was used consistently wrong, so there was no behaviour bug. But the code was confusing because the direction was wrong.

Tests still failing.

- All accessors come up in exception state.
- Read-accessors increase counter in init phase

Assertion is gone, but tests still failing