#558

#559

- Remove all Roboto files

Since there is just one font, this setting can be safely ignored. This 
is easier than sanitizing all elements.

#531

- Background color must not be transparent for the stickied panel to 
overlay properly.

- Use TextImagePanel where possible

- Reformat styles

One as a general label above the table and one for the first column 
heading.

Since this is no proper InputElement separate properties panel inputs 
are used.

#272

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.

Also rename LikertColumn to ColumnHeader, since it is not exclusively 
used by likert.

There were several issues with it's properties, which could not be 
changed.
Now it is properly initialized and prop change get actually handled.

- Units and element are now built via the factory. This ensures only the
  wanted properties are present. All others are discarded.
- Since the sanatizer is supposed to check the unit defintion version
  it is used by player and editor and therefore put in common.
  This in turn makes it necessary to put the JSON resolver settings
  in the root-TSConfig file.
- Renamed a couple of properties to have clearer names.

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.

- Unify font and surface props
- Use intersection type for additional properties
- Also rework editor props panel to properly create the combined 
properties recursively, passing the results to its child panel (tabs).
New algorithm works without lodash, therefore the package is removed.

This removes all the classes and goes back to simple interfaces for
unit, pages etc and all elements. This makes creating them easier and
cleaner.
Things like specific needs when setting element properties and most
importantly compatibility handling is done by a special service module,
that knows all the elements and how to repair old their potentially
outdated definitions.

Remove the wrapper divs in each element component and add the
'fixed-size-content-wrapper' class to the element overlays
of player and editor

The previous solution, which uses a top position of 50%, did not work on
iPad

This is done according to the Angular best practices and minimizes
namespace collisions when using other packages which might use the same
selectors.

Technically the selectors are not even becessary since we use an Angular
component factory to create element components but it is still useful
for the DOM element naming, for debugging purposes for example.

Compound elements are now supposed to use overlays for their child
elements. This overlay makes selecting child components (by clicking on
them) and marking them as selected (done by the selection service)
possible.
The SelectionService no longer needs special logic to handle compound
children selection, as they now also have an overlay with the same
interface as normal (canvas) elements.

A few modifications in connected directives are necessary. The now
handle children components in a proper array instead of QueryList.

Likert elements do not have clickable children yet and work a little
differently. This should probably be unitized in the future.

Elements are supposed to be centred when this setting is used. Since it 
is the same CSS for almost all element components it is put into global 
styles.

Missing components: video, spelling.

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.

No unused space around images and image an text below each each other.

This reverts commit b5d3b810.

The old behaviour with non-scaling images is wanted here. Will improve in subsequent commit.

Also all elements now take the parentForm as input. Allowing it to use 
them with template binding and not only setting the value directly (in 
the controller).

- Images now scale up and down depending on the available space.
- The new property controls the first (column) size parameter for the 
grid. The others are fixed at 1. Decimal values are allowed for 
fine-tuned control.
This prop is passed on to the child likert-row component. It uses the 
same grid and needs this info for proper alignment with the column 
headers.
- Remove unnecessary div in likert

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

Use flex to position image and text below one another. Don't use any 
image scaling setting. Now the images grow but don't shrink.

There were some things missing when renaming questions/answers to 
rows/columns. Now everything is properly named.

Since this is built using a grid it does not need dimensions. In fact it 
having dimensions interferes with styling.

* Add IntersectionService
* Add CompoundElementComponent as parent for LikertComponent
* Inject ElementRef to common ElementComponent
* Rename players' ElementComponent to ElementContainerComponent

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.