it was anyway dysfunctional and mainly slightly reducing performance.

Just use enableDebugDataLoss() to enable debug output.

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

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.

this was never really a problem, since it was always used with the BidirectionalProcessArray() which implements writeDestructively same as write

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.

wip: fix propagation of initial values from control system variables (persistence layer) and device registers (just the current value)

- Exception handling decorator and ThreadedFanOut send condition variable notificatios via the DeviceModule
- FanOut sends terminate to impl and all slaves.
Solves (some?) shutdown issues, but breaks bi-directional array test.

- implement ThreadedFanOut version with return channel
- add test for ThreadedFanOut with return channel

Updated to use the new ReadAnyGroup instead of the old readAny function. Some tests are still hanging or failing (mostly due to shutdown issues)

Renamed Application::testableModeThreadName() into Application::threadName(), since this will be used for other purposes as well.

- add all networks triggered from the same node to the same TriggerFanOut
- put all feeding nodes in a TriggerFanOut into the same TransferGroup

- added some class documentation