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

The readNoNBlocking() to obtain the initial values is now run on all ApplicationModules (incl. VariableGroups) before starting the first module, to ensure the intial values are really processed first.

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

allow specifying the array length for direct connections between device and control system (as the type is already defined in this case)

Adapation to the unified versions of ControlSystemAdapter and DeviceAccess.

Status: Library compiles, tests do not yet compile.

- extended the trigger tests
- removed some debug output

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

- performed some code cleaning and refactoring
- store all nodes in a VariableNetwork in a single list, to allow deciding later if a node is feeding or consuming

This commit is an intermediate commit and has known bugs. Almost all tests are failing and the demoApp is not running. Debugging will be done in a next step.

introduced an operator>> and operator<< syntax to connect network nodes. to realise this, the VariableNetworkNode class has been changed into a pimpl pattern.

Allow to make connections directly based on VariableNetworkNodes. This is a first step, more changes have to be made in this direction.

Use the threaded version of the FanOut if a pushing feeder is distributed to multiple consumers, so all consumers receive updates immediately.

Split the SCALAR_ACCESSOR macro into SCALAR_OUTPUT and SCALAR_INPUT to prevent output accessors to be created in poll mode (which makes no sense). Since some tests were using this, now instead a DeviceAccessor in poll mode is used for these tests.

- fixed a bug in the FanOut which did not wait for the trigger (since ProcessScalar::receive() does not wait)
- fixed a bug in Application::feedDeviceRegisterToControlSystem() not handling the last arugment (trigger) properly
- improved the output produced with VariableNetwork::dump()

added also the consumer-type variables to the XML file

Add some first code to produce an XML file describing the application variables published to the control system. This is not yet doing anything useful for now...

start the synchronisation thread of the FanOut to "convert" a poll-type feeder into a pushing feeder by putting in an external trigger.

Intermediate commit before the weekend: added options to add an external trigger to a network to handle poll and push properly. Currently it does not work properly.

renamed publishDeviceReadRegister() and publishDeviceWriteRegister() into feedDeviceRegisterToControlSystem() and consumeDeviceRegisterFromControlSystem()

renamed publish() and connectToDevice() into more specific feedToControlSystem()/consumeFromControlSyste() and feedToDevice()/consumeFromDevice()