- Implemented but not tested yet
- All existing tests passing

- removed ExceptionHandlingDecorator::setOwnerValidity()

- 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

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.

Fixed getCurrentVersionNumber() and setCurrentVersionNumber() so they always get/set the version number of the ApplicationModule and not e.g. of a VariableGroup.

removed incorrect implementation of operator[] and operator() in ApplicationModule (and use the implementations of ModuleImpl instead)

Proper implementation of move constructors and move assignment operators for all module types (including tests for the assignment operator)

fixed connectTo() so it now uses the dynamic/virtual model and thus obeys e.g. eliminated hierarchies etc.

Fixed some more problems with the move sematics of EntityOwner/Module. Re-registration at the owner was missing and some things were done in the wrong place. Also the move assignment is now back again.

put the move constructor and move assignment-operator into the EntitiOwner base-class and inherit them

introduced a ModuleGroup (grouping ApplicationModules and other ModuleGroups) and enforced a proper hierarchy of modules to exclude that an ApplicationModule can own (directly or indirectly) another ApplicationModule

Changed Module::connectTo() to accept also temporary module objects, e.g. as returned by findTag(). As a consequence, the operators [] and () of the modules had to be changed to const.

Added names and owners for modules, to build a full hierarchy chain. The syntax for creating modules is now not so nice, a better way has to be found (maybe by adding a macro if better solution can be found).

Read all application inputs once before starting the module threads, so the initial values are correctly present.

For this purpose, additional changes were necessary:
- Added support for constant values as feeders and consumers (just ignore the writes)
- Connect all unconnected application accessors to constants after defining the connections and before creating the implementations
- Renamed the user-overridden function "initialise()" into "defineConnections()", since more actions are now necessary during initialise().
- The connections are now made (i.e. the implementations are created) during the initialisation phase

- extended the trigger tests
- removed some debug output