Fixed tests which were broken after updating the demoApp due to changed map files. Now the tests have their independent map files.

A DeviceModule now returns the same VariableNetworkNode when asked for the same register multiple times. This leads to a new restriction that registers can now only be either read or written. This restriction can be mitigated by using the logical name mapper to create an alias of the register. This has been implemented for the tests and the demo application.

- allow setting the "eliminateHierarchy" flag in the constructor of a module

This is an interface change which was done in an incompatible way!

Rebased the ScalarAccessor and ArrayAccessor classes onto the mtca4u::NDRegisterAccessorBridge class.
Known problems present: code compiles but tests do not run

Removed the macros for defining accessors and introduced convenience classes instead. This adds slightly more syntactic sugar, but also allows more flexibility and seems to be a more coherent interface.

This commit incompatibly breaks the interface with the previous versions. Since ApplicationCore is not yet used in any productive environment, no compatibility is provided.

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

Added description field to the variables. It is currently ignored and will be added to the XML file in a next step.

Refactored the tests so that all modules are inside the application classes. Otherwise the shutdown scheme might break at some point.

- extended the trigger tests
- removed some debug output

Introduced the DeviceModule class which provides an interface to obtain VariableNetworkNodes for device registers

move the device test out of the AppModuleConnections test into its own executable and split it into a feeding and a consuming part