Include descriptions of the owning Module in the descriptions of each process variable to make them more complete.

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

Use one file per class. Also, use boost::core::demangle instead of
checking for abi::__cxa_demangle by ourselves.

We have a visitor now for generating
 - the XML
 - the Module's dot graph
 - the textual dump of the VariableNetwork
 - the dot graph of the VariableNetwork

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.

fix running into an assertion sometimes: getQualitifedName() should also be possible if the highest hierarchy is a Module (e.g. a VirtualModule)

Make Module::connectTo() no longer a template, since a virtual function can anyway not be overridden with a different return type... (c.f. the comment in the deleted code)

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

made Module::connectTo() compile-time polymorphic, to allow special modules with operator() returning a different type.

Changed Module::readAll() to read all push-type variables first, to make sure that poll-type variables are up-to-date upon return

moved group read/write and []/() oprerators from the VariableGroup class into the Module class, to make the functionality also available in ApplicationModules

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.

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

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67054

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

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