- Model constructors (elements, unit, page, section) now have a 
dedicated parameter, which makes sure all properties are set and valid. 
This way the player can instantiate models without having to interpret 
the values. Any interpretation is done only by the editor, which now is 
solely responsible for creating defaults/blueprints for new elements. 
Models can no longer be created by incomplete paramaters.

- Also refactor Stylings to have sub groups for common styles

- Remove dynamicPositioning from PositionProperties. This is not 
knowledge that the element needs to know. In the few places it was used, 
it was fixed or solved by asking the containing section about which 
positioning is active.

- Fix and improve cloze child sizing. All can now have dynamic width and 
height.

- Fix empty lines in ClozeDocument rendering

- Editor SelectionService now knows if a cloze child is selected. This 
way the PropertiesPanel can show valid dimension inputs regardless of 
the underlying section.

- Basic implementation

Also restructure files containing interfaces.

Measure holds the value and a unit for CSS properties.

- Replace Material Droplist with native HTML events
- Remove simple-drop-list element; Cloze elements now use the normal 
DropList element
- Add example units

- A HotspotImage has an image and divs placed on it, which are used
as hotspots
- Inherits from FormElementComponent, which is why the hotspots are kept
  as a list in the value property.
- Can be validated as required and uses its own custom validator

The unit tests errored out because of circular dependencies via the 
Elementfactory class. Therefore:
- No longer creates styling/position/player-Properties. This is done in 
the Element parent class.
- Move element creation from Section to the ElementFactory class 
instead.

- Make position props on buttons optional
- Move UIElement creation back to Factory instead of within Section

- remove ID handling from model classes. This is now done by the editor 
itself (mainly unit service).
- Rename and move IDManager to editor as IDService

This is only useful in CompoundElements. So use checks for that class 
instance.

#318

Remove 'any's be adding proper types and using 'never'.

- problem with nullish values

Now properly finds all normal and simple drop lists.
This is achieved by a new method of unit all it's sub-components, which 
returns all contained elements with and optional type filter.

Also improve (still not very pretty) styling of the drop list props 
panel.

#260 #259

- Elements initialize their fields explicitly and not with
  Object.assign, since Object.assign also assigns
  (and therefore overwrites) parent fields.
- IDService is no longer an Angular service but a basic singleton. This
  allows to use it in classes.
- The IDManager can be optionally passed to unit and element
  constructors. When present the elements check and fix their given ID
  when created.
  This way elements can be created without depending on the external
  IDManager but also with the dependency.
- ElementFactory is no longer used to create elements. Those are now
  either created directly via 'new' or via the Section, which knows the
  different element types.

Elements read as classes were overwritten by the plain objects passed to 
the constructors.

This way elements can handle their logic themselves without having to
rely on outside utility classes.

Also restructure files in common in a more logical way.

This removes all the classes and goes back to simple interfaces for
unit, pages etc and all elements. This makes creating them easier and
cleaner.
Things like specific needs when setting element properties and most
importantly compatibility handling is done by a special service module,
that knows all the elements and how to repair old their potentially
outdated definitions.

- Move the method to the unit service, so the proper 
updateElementProperty method can be used.
- Also improve the logic, reducing variables.

This makes for cleaner imports.

Was not correctly creating new instances of non-primitive values. Now
uses "JSON.parse(JSON.stringify(element))" for deep copying the element
first.

Also refactor by moving the method to the UnitService, where all ID
handling should take place.

The given serialized properties may not conform to all UIElement 
properties. They are merely meant as a building plan; they may also 
contain outdated properties which have to be transformed when reading.

The problem being solved is that compound-sub-elements must not have
all the properties other elements have. For exampe positioning info.
Sub-Elements are positioned inline. To avoid having similar class
inheritance structures for positioned and inline elements, we use
interface. Positioning is done via interface and is therefore optional.

Those optional properties are kept in an object in a variable. This
allows to hide specifics from element classes and removes the need to
initialize all the fields in every class using the interface.
The elements mostly care about their own specific properties anyway.

The same technique is used for font and surface elements. Here we also
don't want to initialize all the styles in every class.

Changing values of element properties works like before. Just set the
property as if it would be a direkt prop of the element. The element
itself puts the value in the currect sub-object (positioningProps,
fontProps etc).

For reading the values there is a similar method, but it is not used
anywhere by now. Since the properties panel operates on the raw values
anyway (refer CombinedProperties) and for element components this would
mean calling a function in the template, which caused change detection
to run the function very often and is therefore bad practice.

Additional notes and refactorings:
- Restructure all files in common. UIElements in the same folder etc.
- Move all interfaces to the UIElement file. This avoids circular
  imports, which would be needed to allow PositionedElement to extend
  UIElement.
- Interface initializers also handle reading values in the old form.
- Add PositionedElement for use in canvas overlays. This is a UIElement
  with guaranteed postionProps.
- Don't export all Material packages from common, only the ones
  used in player and editor. The rest is only used in common and
  does not need to be exported.