Drop lists that allow only one element but are not used in cloze texts
display their elements right-aligned

- Mainly highlight border and moving elements.
- Centerpiece is: line-height: 130%;
  Don't know why or how but it works okay.

Rules for when drop is allowed have been fixed. It is quite complicated 
and therefore a lot of explanatory comments are added.

- improved translation
- add example file

Allows DropListvalueObjects which have this setting to be replaced in
lists which only allow onlyOneItem. When this switch is set, the class
sets the other 2 internal values
(originListID?: string; originListIndex) itself. Those can not be seen
nor changed from outside.

Also refactoring in lots of places around droplists. Better names, 
cleaner structure, comments.

#305

Lists with this setting delete dropped value objects. This allows 
putting items back.
(Only makes sense when used with copyOnDrop. Otherwise there can not be 
duplicate value IDs).

Also improve constructor value checks to correctly handle nullish 
booleans.

#281

#309

Otherwise, no elements can be dropped at this place

To detect if a custom form element was touched it is necessary to set a
custom tab index

Use the source list placeholderIndex instead of the index for the target 
list.

Chromium does not allow DOM manipulation on dragstart. Therefore add 
timeout.

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

- 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