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.

They will be reused by the player.