The unit definition now has 2 meta-fields: 'type' and 'version'.
The former has the fixed value of 'aspect-unit-definition'.
The latters contains the version without any prefixes, i.e. '1.2.3'.

The sanatizer tries to read the versions of older formats as well and
uses the found version. This is important since the handlePlusOne
method must only run of a specific version (in the old format).

The sanatizer no longer shows any messages and therefore does not need
the MessageService anymore. The information about whether sanatization
happened or not is returned as second parameter for those that are
interested. The editor is, the player is not.

The editor API service now constructs the 'unitDefinitionType'
parameter from both values, resulting in something like
'aspect-unit-definition@1.2.3'.

- Units and element are now built via the factory. This ensures only the
  wanted properties are present. All others are discarded.
- Since the sanatizer is supposed to check the unit defintion version
  it is used by player and editor and therefore put in common.
  This in turn makes it necessary to put the JSON resolver settings
  in the root-TSConfig file.
- Renamed a couple of properties to have clearer names.

Remove manipulations from elementModel
- Refactor drop list component
- Use of initial values for audio and video playback time

Defining the validators not in the elements anymore, but when creating
the forms

This makes for cleaner imports.

Since the array of 'ClozeElements' can be empty, it must be checked

The factory was ignoring the src parameter, which is set before by the 
UnitService.

- Unify font and surface props
- Use intersection type for additional properties
- Also rework editor props panel to properly create the combined 
properties recursively, passing the results to its child panel (tabs).
New algorithm works without lodash, therefore the package is removed.

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.

- 'hideOtherPages' is not supported by verona api
- 'uninterruptible' is already fulfilled by disabling pause and
progress bar

The copy is needed to not have cross references between elements.

This allows elements in dynamic sections to have fixed dimensions.

Some modifications to property panel logic, to show dimension fields and
proper labels.

Only implmented in dropList and button elements.

- Use the same default state for interactiveMuteControl
and for playerProps.interactiveMuteControl

Variable naming, reorder imports etc.

This makes for cleaner imports.

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.

Basically a div with border properties as usual.

The interaction can now be turned off without hiding the button.

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.

The explicit check for undefined ensures that the value 0 of a
number property is taken from serialized elements.

Similar to a text element but parses the text on change an replaces 
markers with actual elements.
The text is then displayed inline with the elements.

The explicit check for undefined ensures that the value false of a
boolean property is taken from serialized elements.

This element has a list of string as editable options. Those strings 
form draggable elements which may be reordered or moved between 
different DropList elements.

Also refactor option change logic to allow any property not just the 
text property.

This works similarly to the standard radio group, but has a fixed 
horizontal layout with images above the options.

This way the color-input element can read the color and show the correct 
preview.