Remove the wrapper divs in each element component and add the
'fixed-size-content-wrapper' class to the element overlays
of player and editor

The previous solution, which uses a top position of 50%, did not work on
iPad

This is done according to the Angular best practices and minimizes
namespace collisions when using other packages which might use the same
selectors.

Technically the selectors are not even becessary since we use an Angular
component factory to create element components but it is still useful
for the DOM element naming, for debugging purposes for example.

- Simplified the code logic. Verification is done once in the beginning 
and not on every element.
- Now uses semver to verify and compare version strings

Better solution without an extra variable.

ImportModuleVersion stores the unitDefinitionType of the loaded unit
definition. During the initialization of the unit, the individual
elements can react to the stored value.

and DropListSimpleElement

This is not a complete backwards compatibility. Only the value "0" can
be safely classified as false. It is therefore set to "1".

Now correctly creates child elements for every marker it finds.

Updated the TipTap extensions to use model instead of just the ID.

Also improve interface naming.

Regenerate IDs for child elements. For this we use the child element 
list we have to produce for the player anyway. To be able to use it, it 
has to move to the element though.

Only the overlay can be clicked. This way the statre of the elements can 
not be changed which might be confused for actual value changes. Those 
can still only be done via properties panel.

Unfortunately we need another variable so the cloze elements knows when 
it runs in the editor or not.

This way the placeholder is exactly as big as the font size. There is no 
space for a padding here, as the normal dropList has.

Frames are supposed to be used to group other elements and therefore 
usually needs to be behind them.

- Remove element as parameter

Compound elements are now supposed to use overlays for their child
elements. This overlay makes selecting child components (by clicking on
them) and marking them as selected (done by the selection service)
possible.
The SelectionService no longer needs special logic to handle compound
children selection, as they now also have an overlay with the same
interface as normal (canvas) elements.

A few modifications in connected directives are necessary. The now
handle children components in a proper array instead of QueryList.

Likert elements do not have clickable children yet and work a little
differently. This should probably be unitized in the future.