fix tsan complaining about incrementing/decrementing testableMode_deviceInitialisationCounter outside testable mode

- Also removed race conditions in the test.

- Version number in exception case is always the same.
- Remembers that it has reported an exception so a readLatest() after recovery does not switch the data validity back to ok if there was no new data.

- 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()

Lock is only released for accessors with wait_for_new_data on blocking
reads. This fixes usage of readLatest() in testable mode.

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

Removed obsolete localValidity.

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.

- 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

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

Rearranged processing of fanouts and their consuming nodes. A list of
consuming nodes and implementations is passed to the fanout constructors,
so the nodes don't have to added later. This resolves conflicts in the
order in which accessors are decorated and added to the fanouts.

FanOut constructors could still use refactoring.

- removed ExceptionHandlingDecorator::setOwnerValidity()

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

Ongoing refactoring. Consuming fanout works again.