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

restored write functionality of MetaDataPropagatingRegisterDecorator in case of locally set faulty status (DataValiditySpec 2.1.5)

Implemented testFaultReporting

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

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

wip: changed constructor of ExceptionHandlingDecorator to have a VariableNetworkNode as argument instead of a bunch of details

wip ExceptionHandlingSpec: C.2 ExceptionHandlingDecorator is throwing…

It is now inferred from the TransferType in doPostRead of the
MetaDataPropagatingRegisterAccessor, if the owning module's
version number gets updated.