- Implemented but not tested yet
- All existing tests passing

Prints a clear message if a circular dependency of initial values exists.

Poll-type reads are blocking until the initial values are available, hence the testable mode must be released in case the initial value is not yet available.

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

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

- removed ExceptionHandlingDecorator::setOwnerValidity()

In terminate(), call interrupt only when wait_for_new_data is set

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

Assertion is gone, but tests still failing

  - Rewrite on exception counter change
  - getDataValidity respects exception and dataFault counters

  - EntityOwner has individual counters for both events
  - Adapted all instances of increment/decrementDataFaultCounter
  - Not changed getDataValidity() implementation yet
  - Tests failing

change declaration of 'decrementDataFaultCounter' in 'EntityOwner' to take a bool parameter and adjust rest of the code to it
implement 'decrementDataFaultCounter' in 'ApplicationModule' according to ticket #95 -> rewrite all outputs when 'faultCounter' goes from 1 to 0

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

TestableMode: ApplicationModule guarantees that the main loop thread had the testableModeLock at least once. Solves #66

move ApplicationModule::appConfig() to ModuleImpl::appConfig() so it can also be used from ModuleGroup

Implemented first part of #17: A HierarchyModifier can now be specified instead of the eliminateHierarchy boolean flag. No new functionality is yet added.