The elements z-index is no longer ignored.
Isolation helps for having negative z-indices. Those elements no longer 
are hidden behind parent elements.
The helper grid need to have a large negative z-index to not interfere.

Also restructure files containing interfaces.

Measure holds the value and a unit for CSS properties.

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.

Components with bigger scope are put to the component root, canvas, 
props panle and new-element-panel.

Change import paths of CommonModule files in editor and player

This makes newly created elements appear next to each other instead of 
on top.

This is now done only via the cdkDropListGroup directive which collects 
child drop lists. There is actually no need to connect them manually.

Fixes: #203

gridColumnStart: number;
gridColumnEnd: number;
gridRowStart: number;
gridRowEnd: number;

becomes

gridColumn: number;
gridColumnRange: number;
gridRow: number;
gridRowRange: number;

Improve code and prohibit resizing of section when child element is 
dragged.

Now uses the implicit grid in auto mode.

Now named just position.

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

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.

Ignore grid sizes when dynamic mode is active.
This has the added benefit of adding some actual dynamicality to the 
grid in the editor.

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.

The dropListList generation is now done when things are changed via the 
section menu and no longer on element update via unit service.
Also remove some interfaces to avoid circular imports. The interfaces 
are so small and insignificant that their form might as well be 
specified at usage point.

This allows to select elements without clicking them on the canvas, as 
elements may be obstructed or not visible for some reason.

The selection logic is a bit complicated because usually only the 
overlay components are usd for selection which are also the place to 
apply any highlighting on. Here we have to find the component element 
reference from the section. Therefore the double looping 
'getElementComponent' method.

Also when an elements is selected it briefly gets z-index 100 so it is 
moved to the front and visible and manipulatable.

Broke during the refactoring of the element models. Now correctly uses 
the positionProps field.

Also improve variable naming.

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 reverts commit c71cf1a2.

Need to bubble the event further up to where there is a section 
reference.

This structure moves closer to the structure template the team decided
on. Components and services are kept in dedicated folders instead of
following the logical code structure. This is still not the case here as
the unit-view component is still nested, but it's closer.

Some things had to be tweaked in regards to positioning and sizing of 
elements.
The drag preview is now done with a separate div, which only shows while 
dragging and has the temporary dimensions of the element. When dropped 
it sets the grid values if the dropzone as before.

Use proper types and remove unused vars.

Less intrusive colors and border style.

The main components are right at top level and the directories below
mimic the data structure (unit->page->section).
The toolbar is only used in dev mode and does not belong directly to the
unit view.
The TextEditor is a complex component and deserves it's own directory
even though it is used within the unit-view. Might be refactored to its
own module later.

Can now be repositioned and moved between sections properly.

- The selection service only needs to handle element selection. For
pages and sections having the index is enough.
- Those indeces are simple fields instead of observables. This also
simplifies the components which don't have to get the value out of the
observables.
- Therefore the selection service does no longer need to have a direct
reference to the unit service and it's unit.
- Selection logic is not done by the section components themselves but
by the parent canvas component.
- The unit service can now manipulate pages and section by index in
addition to passing the necessary objects directly.