This is the implementation for the specification change done in a recent
commit.

The previous implementation using the mutex had two issues:

1. The mutex was locked in a different thread than unlocked (DeviceModule constructor vs. handleException() thread). This results in undefined behaviour.
2. The boost::shared_mutex::lock_shared() function is not an interruption point, so applications did not terminate while waiting for initial values. (boost::latch::wait() is an interruption point.)

This needs to be done here since the recent changes in DeviceAccess, see comment for reason.

This reverts commit a80ebc2d.

This was the wrong approach, see ChimeraTK/DeviceAccess-DoocsBackend#45

This helps understanding where an error is coming from, e.g. when multiple devices are used in the same logical name mapped device

remove unnecessary and wrong (not thread safe) increment+decrement of the testableMode_deviceInitialisationCounter

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.

- 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

- removed ExceptionHandlingDecorator::setOwnerValidity()

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

This reverts commit d025bb5a.

This partly reverts d5ab1447, where the existing doReadTransfer overrides
were removed. This commit gets the existing implmentations back, but
changes the function name to doReadTransferSynchronously.

Remove functions that do not exist anymore

ExceptionHandlingDecorator: doReadTransferNonBlocking() and doReadTransferLatest() must always return true because there will be new data. The recovery in postRead() takes care of it.