Also reorder translations a bit.

Options and value were the same thing anyway and the value was updated 
once anything was changed within that dropList.
The player though needs a start value and this way we have one.

Interactions are mutually exclusive (for now). The string values 
describe which interaction is possible.

Supplement to commit "Refactor elements to use the model's value"

AudioComponent and VideoComponent inherit from
MediaPlayerElementComponent to avoid duplicate code

This change mainly helps the editor.
The idea is to make the element components have the correct value of
their model and don't rely on the formcontrol value. The formcontrol
can be hard to manipulate, especially in compound elements. Setting
the model value is way easier.

The formcontrols are kept and should not interfere.

- Add background to dragged element via cdkDragPreview
- Add placeholder box for dropping via cdkDragPlaceholder
- Add animations for transitions when dragging and dropping

Since the options of the DropListComponent are now managed as values,
the DropListComponent can be treated as a standard FormElementComponent

Although the DropListElement is a FormElement, its value is represented
by the field options. Therefore, this state must be saved.

The drop listener simply does nothing when this is set. This way it is 
still possbiel to drag item but dropping them has no effect.

Does no longer change the options instead of the connectedTo array. I 
reworked some logic that before only changed the options to now be able 
to handle any kind of string list.

Improve detection of valid pages, sections and elements

It needs row and column to work. (It is using flex in the background.)

Use 'horizontal' and 'vertical'. Which are better terms and also align 
with other element's values.

Also improve conditional border style. The additional dragPreview is 
needed so the dragged item does not have the border.

The width/height of 90% are a preliminary workaround to not produce 
overflow with the border. A better solution would be good.

In the UI. Internally it is still likert.

The player-element dialog options did not show the field, even when it 
has a value. Now it properly checks of the existing config has this set.

This element has a list of string as editable options. Those strings 
form draggable elements which may be reordered or moved between 
different DropList elements.

Also refactor option change logic to allow any property not just the 
text property.