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.

- Remove TODOS

elementModels are described in the unitDefinition
elementCodes are saved in the unitState

Their values are mapped by the ElementModelElementCodeMappingService

- Rename class name, methods and properties
- Remove method registerDropListValueIds
- Calculate array of DragNDropValueObjects in app component

Use the mapper method `toUnitState` of the UnitStateElementMapperService
when registering elements and their initial values

- add unit-definition-menu module
- add verona module and move verona services and verona interfaces to it
  to make them available in different modules
- move the distinction of different page types to app component to make
  them available for unitDefinitionMenu component

Change import paths of CommonModule files in editor and player

- Use `inputmode` 'none' to hide the virtual keyboard of the os
- Use DeviceService to detect if the player is running
on a mobile device

This can be enabled for TextFields and TextAreas and shows a keyboard
at the bottom of the screen. This does NOT set the field to read-only
which is probably wanted in a situation where the system keyboard is not
to be used. For flexibility purposes it is not implicitly set and needs
to be set manually. The same goes for other input assistance settings,
which should not be used in addition to the keyboard but it is allowed.

The keyboard has an extra switch to additionally show french special
characters.

Rename KeyboardComponent to KeypadComponent
Rename KeyboardService to KeypadService
Split LayoutComponent into LayoutPlayerComponent and
LayoutPagesComponent
Prepare the introduction of an additional keyboard

Reduce the number of input parameters in FloatingKeyboardComponent
Move double-used method to KeyboardService

- Reimplement UnitStateComponent as central point to send the collected
information
- Implement ValidationService to determine the responseStatus of all
forms

This was necessary after the surrounding element container with its
styles and classes was deleted

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 helps to divide the code of the element container into smaller
meaningful units.
In addition, each element can be given its own form group.