revert last commit, cascading ApplicationModules should be avoided instead (and should be prevented in future)

added function to obtain the qualified name of the variable, including the hierarchy path. not yet used.

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

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

added function to flatten teh hierarchy, renamed eliminateHierarchy() into setEliminateHierarchy() for better clarity

added preliminary support for tags to application variables which can be searched for and used to generate virtual modules

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

- Default constructor for Accessor exists now
- A function Accessor::replace() allows to assign a new accessor
- For clarity/safety: copying accessors using the assignment operator is now forbidden
- The destructor of the accessor unregisters it from the module (to allow temporary accessors)

added function to obtain list of accessors from modules recursively (i.e. including accessors from sub-modules)

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