- crossOutChecked adds line-through styling if checked. This is used in 
Cloze texts to cross out words.
- This means Checkbox is no longer a PositionedElement and does not 
validate PositionProperties

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

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

- When the height of the child elements of a cloze element is increased,
they all now grow out of their center

- Extra span element around cloze child elements served no visible 
purpose. It also makes sense that an inline div is not inside of a span, 
which is meant for text.
- CSS rules were overengineered and in part shadowed (and thereby 
pointless) by element styles from the template.
This is also in preparation for the DropList styling overhaul.

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

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

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.

This reverts commit d053d03c.

This feature will first be developed properly in a branch.

Cloze documents now use this correctly.

Instead, use Textfied component with the property isClozeChild

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

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.