#691

- Due to the width of the scrollbar, text areas change their inner width
under Chromium when the scrollbar is displayed. The use of offsetWidth
instead of contentRect ignores the presence of the scrollbar. The
calculation is therefore less accurate, but sufficient for estimating
the number of rows

#662

The CSS selector for what the element to color changed (most likely with 
the Angular Material update). Also a lower z-index is needed to not 
cover the text.

#534

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

Also restructure files containing interfaces.

Replace resize event listener with ResizeObserver to also detect size
changes of the surrounding grid

- Replace UpdateTextareaPipe with DynamicRowsDirective

The dynamic height of the textarea is calculated based on the available
width. However, accessing the width of the textarea often results in an
error.
For this reason, the calculation is now done using resize and change
events in conjunction with a timeout to wait for the textarea to render.

- If this property is set, the input of more characters than specified
in maxLength is prevented
- It also prevents the insertion of text.

- Reduce redundant code
- Prepare implementation of input limitations

Move deps only used by geometry to the geometry class and out of the 
parent.

DomSanitizer was a relict and no longer in use.

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

- Remove prefix 'on'

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.

- A new new editor component has been created for this, which has a
reduced interface and produces span-elements instead of paragraphs.
- Since the created HTML (span with CSS) is regarded as potentially
harmful it needs to be sanitized. For element components the sanitizer
is put in the abstract parent element-component-directive.

Replace the direct method calls in media player components with events.
For this purpose, expand the inputs of the media player components that
are defined in the ElementMediaPlayerGroupComponent.

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

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.

Prevent sending a valueChange notification

Use a border with border-radius set to make it look nicer.

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.

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.