- overflow of lists is now hidden to prevent dropable elements from
being displayed outside the container
- placeholders are hidden with flex orientation

Use a horizontal aligned placeholder for dynamic aligned drop lists
when there is more than one element in the list

- Refactor variable of the placeholder dimensions

- Important for vertically positioned drop lists
- Analogous to the calculation of the height

- Replace pixel calculation with percentage values
- Use of only two modes: full fill or line

- This makes the behavior identical to real form elements
- To trigger the focusout event, the HTML element needs
the tabindex attribute

The dragged image did contain carry information about it's element.
Also remove useless drag and drop functionality for the placeholder.

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.

- Fix DropLists with copyOnDrop to display a placeholder copy of
dragged elements.
The drop preview is hidden on those lists. It still has to be in the DOM
to be the target for the 'falling' animation of the dragged item,
otherwise it flies to the top left corner of the viewport.

With this setting elements are copied when being dropped to another 
list.

On drop it is also checked if the item-ID is already present in the 
list. If it is the drop event is silently discarded. This allows putting 
items back in the list without creating duplicate IDs.

Lists with this setting:
- do show a placeholder of the items being dragged. This way it is 
conveyed that the item will remain there after being dropped.
- don't show a placeholder when items are hovered over them, to avoid 
confusion with duplicate items.

Sorting within DropLists is disabled, since it causes moving items 
within the list. It has to be discussed if this feature is even needed.

The height of an empty droplist can't be calculated on ios 14
because it's in a flex container

- 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

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

Remove the wrapper divs in each element component and add the
'fixed-size-content-wrapper' class to the element overlays
of player and editor

The previous solution, which uses a top position of 50%, did not work on
iPad

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.

Elements are supposed to be centred when this setting is used. Since it 
is the same CSS for almost all element components it is put into global 
styles.

Missing components: video, spelling.

Outline may be shown when valid dropLists are highlighted. The bottom 
patr of the outline is cut off when the whole width is used by the 
dropList.

Section was picking up the size of children elements. With relative it 
works.

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.

This new setting makes child items space around in a row with line 
break.

Images in vertical alignment now always reserve the whole row and don't 
appear next to each other.

Now only sends a list with IDs as value. The actual list manipulation is 
done with Material helper functions (transferArrayItem...).

Now correctly used the value of the dropped element.

- Dnd values now have a special type that has an ID, a string and
  another string for an image path.
- A new dialog exists for editing thoe options. Similarly to the likert
  header.

This is the same hack used in the editor for overlay elements. Here 
applied to the actual dnd elements seen in the player.

Explanation: The cursor can not be applied to the dragged elements as it 
is not positioned (at least that is my understanding). The workaround is 
to style the body (cursor) while anything is being dragged.

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 allows to use them in template bindings. Used in compound elements.

- List items only have a margin between then but no longer on the 
outside.
- Remove unused background color. This is set dynamically in the 
template.