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

changed again the interface of SplitArray: the number of groups and elements per group don't have to be a template parameter, instead they are now specified in the constructor

ConfigReader: make exception what() message more elaborate when not finding a variable in the config file in get()

Extended the SplitArray modules to also allow splitting into multiple arrays of the same size. This breaks the interface of the old modules, but they were not yet used anywhere so this should be ok.

Fixed a bug that sometimes variables were read (resp. written) in groups despite they were outputs (resp. inputs). This was happening with device variables since they are bi-directional. Now no longer the information from the accessor is used whether this variable is readable or writeable, but the information from the VariableNetworkNode which direction this variable should have.

configuration variables are now provided to the receivers right away without any read(). Updates will never be sent.

allow obtaining the config values already before connections have been made through a speicial get() function

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)

- removed the no-longer-necessary optional argument of findTag() - use flatten() instead

obey the eliminate hierarchy flag when using the () and [] operators of modules (and thus also when using connectTo())

refactor ArrayAccessor and ScalarAccessor: split off common code and put into common base class InversionOfControlAccessor

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.