Instantiate the child elements coming from the editor (i.e. when the 
document changes). Otherwise the cloze children are all on the same 
object reference.

#513

- Can also be used with other elements

The ClozeDocument needs properly instantiated UIElements for the custom 
elements.
Instead of creating a new ClozeDocument on the basis of what TipTap is 
producing and replacing the custom parts with instances, the 
ClozeDocument is kept in place but the custom parts are collected into a 
list and changed there.

#450

In Player-context the constructors are to fail, when the given 
properties are not exactly as expected. Therefoore they are validated. 
When this validation fails, an environment variable is checked to 
determine if the element should be created anyway with defaults. This 
switch is off in player-context. But the Editor is not so strict and can 
create elements with incomplete parameters.

There is also a new VersionManager which checks given unit definitions 
for version-validity. Upon failing this check Player and Editor show 
error messages.
The Editor accepts a certain unit definition version, but shows a 
warning.

The Editor checks units for invalid references after loading. If any are 
found, they are removed and an info-panel is shown.

#512

- Remove SanitazationService from player
- Extend interface ButtonEvent

- 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

- Only elements with this property are considered in the player when
determining the presentation state
- Add the registration of CompoundElements at the UnitStateservice
- Fix visibility handling of section with simple rules

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

- Background color must not be transparent for the stickied panel to 
overlay properly.

- Use TextImagePanel where possible

Toolbar is a single word, therefore any capitalized letters are errors. 
No need to sanitize, since this was broken anyway.

#384

#386

#452

... to create a new reference for options property.

Measure holds the value and a unit for CSS properties.

- There is a page navigation only for not always visible pages
- Fix initialization of the button's action parameter

- allowReplacement (moved from element to list prop)
- originList and Index are non-optional (means placeholders have to be 
used sometimes)
- Re-introduced the dict of all DropListComponents. This is the only way 
I have found to get a reference to a DropListComponent by ID. This is 
needed for returning to origin. Origin is not actually part of the 
transaction and needs to be fetched from somewhere else. Hence the dict.

- Console statements still present for debugging.

The native browser-drag-and-drop does not work in tablets. Therefore 
back to Material which works.
Features are moved over with the exception of replacing items.

- Copy-Lists now always allow putting items back.

- Renew example files
- Update versions and notes

- text field simple
- toggle button

(The array reference must not be destroyed)

- Add cdk scrolling strategy to keyboard that brings overlays to
scrolling