- Add pipe to decide which list to use

Uses external software 'MathLive'.

Distpacker issues with mathlive have been solved in a custom 
distpacker.ts in scripts-folder. This is now used instead of the 
distpacker from the npm package.

- 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

Create new pipe for checking if element is included in list.

Using the html property "disabled" results in a warning message in the
player when reactive forms are used at the same time.

ViewEncapsulation.None is required for overriding tooltip

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.

- Split text field and drop list, so they can have differing props
- Improve their dimension default values
- Improve alignment of all cloze children components
- Add dynamic width parameter of toggle buttons to dimension properties
panel. Therefore the postion tab can always be shown and no longer needs
a condition.

Instead, use Textfied component with the property isClozeChild

This helps to divide the code of the element container into smaller
meaningful units.
In addition, each element can be given its own form group.

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.

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.

- Implement marking buttons as toggle buttons

Is now able to interpret more stuff from the editor. The only thing 
missing are the list styles.

- Now only has a variable 'document'. This holds the HTML representation
  in an object. This object is enriched with element models.
- Because the the TextEditor extension can neither create multiple
  element instances nor use the IDService to generate their IDs, this
  has to be done afterwards. See ClozeParser.
- The cloze element has rather extensive compatibility handling because
  cloze elements used to save an actual HTML representation. This has to
  be transformed to JSON/object. Therefore we replace the old backslash-
  markers with custom HTML tags. The editor object does this
  transformation. It needs some custom extensions to recognize (and
  don't remove) the HTML tags though.
- Cloze now shows a placeholder text when empty
- The cloze component needs a small pipe to extract text formatting
  options from the paragraph parts.
- For getting the child elements for the player the models have to be
  extracted from the somewhat complex (JSON)document.
- Added some rudimentary interfaces for the TextEditor document format.
- Removed the old ClozePart interface. This is quasi part of the new
  interfaces.

This is meant solely as a cloze child as a representation of a radio 
button functionality.

Basically a div with border properties as usual.

It is meant to be used as inline positioned (sub) element. Therefore it 
has not postioning information and less property options than the normal 
drop list. Similar to the simple text field.

MatButtonModule is used in all projects!

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.

This is a native input element which is used in cloze elements. Here 
(sub)elements need to be positioned inline, which is hard to do with 
material components.

Also add a method to all form elements to set their form value, which is 
now only used by the simple text field but may be useful for other 
elements, which don't integrate in material form fields.

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.