SHould now always correctly line up with the text even on different line 
heights.

This allows to use them in template bindings. Used in compound elements.

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.

The condition did not respect the case of null value.

Make radio button and first line of the label (in case there is a line 
break) appear at the same height.

This makes it so that other options appear with strikethrough when one 
is selected.

For elements which don't have this functionality the workaround is to 
use pointer events and make the elements unclickable.

Add 10px margin between label and options.

Other elements do implement the interface but do nothing with the 
property. This make all the interface handling a lot easier at the cost 
of having useless variables in some contexts.

Margin between lines and between button and it's label.

Saving the actual drop down value did not work with duplicate option 
values.

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

* When elements receive the focusin event, their status is changed to
`TOUCHED`
* Replace `this.form.valueChanges` subscription with
`this.unitStateService.unitStateElementCodeChanged` subscription

* Adapts their appearance to mat-form-fields
* Fix coloring of background for checkboxes

Overridden by some child elements (TextField, CheckBox)

* Delete validation message component
* Use instead `mat-error` inside element components to take advantage
 of `mat-input-field`
* Add get validators method to each form element component
* Display validation messages via `error-transform` pipe

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

This is in preparation for dynamic layouting.
The actual dimensions are set by the overlay component which differs but 
is existent for both editor and player.

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.

* When creating components for each element a
`ValidationMessageComponent` is also generated dynamically
* Prepare usage of default values for form elements
* Add `form.ts` for form specific interfaces
* Rename some variables and properties

Use `elementModel.label` instead of `elementModel.text`

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

Use `parentForm` input in `PageComponent` and in `SectionComponent`
instead

* Introduce `FormService` to provide communication between
element components and form
* Add `ngModelChange` and `formControl` to
some element components. This functionality is not used by
the editor

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.