If the property is set, the video will be scaled as far as its
container (static element or grid) allows, otherwise only up to its
maximum native size.

The latest changes to the events for the control bar have so far been
implemented only for the audio component

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.

In ControlBarComponent the property project replaces the property
isAspectPlayer. It ensures that delays are used only in the player
and hints are always visible in the editor.

All elements now use the elementValueChanged event. Also
formValueChanged is changed.

AudioComponent and VideoComponent inherit from
MediaPlayerElementComponent to avoid duplicate code

* Remove FormService Injection
* Move FormService and form types to player
* Move interface ValueChangeElement to uI-element.ts
* Use interface InputElementValue instead of
string | number | boolean | null

- Remove interfaces
- Add classes for all elements as well as unit, page and section
- 2 intermediate interfaces are kept. They dont constituate a viable 
object but only additional properties, like background-color. Those can 
be added as interface to all elements. Initialisation has to be done by 
the element itself though and not by some constructor higher up.

* Remove unnecessary styles
* Refactor case distinctions
* Improve styles of some elements

Consider the available space for width and height
Increase their default heights

The urls must be declared as trusted to be accepted by the application.

Also refactor a lot of stuff belonging to this:
- You can edit the default values via properties panel
- All elements now again have a common parent directive. form elements
have a special parent for forms.

* Only elements which has to be registered by the player's form inherit
from `FormElementComponent`
* Element components use their specific `elementModel`
* Rename file for `FormElementComponent`

The UIComponents now only have the properties they can make use of. This 
means that the angular components use the CSS properties explicitly 
instead of having all kinds of useless CSS properties.
Also it is no longer needed to update the CSS styles via event because 
Angular's change detection takes care of that.

This makes the actual component elements agnostic to any drag and drop 
and selection logic, which is handled completely via the 
wrapper-overlay. Now the component elements can be easily used by the 
player.

They will be reused by the player.