Use selected page index for similar functionality.

Also add section prop editing.

This does not need to be an observable as it is used only internally and 
in 1 component, which needs the new state only after calling update 
functions. Those functions can return the new value directly instead of 
via observable. And for store internal use a simple variable is 
sufficient.

The Material drag and drop stuff does not play well with the 
implementation of elements being styled dynamically via CSS. The extra 
div element pulls them apart avaoiding problems.

This was caused by an internal sorting mechanism of the drag and drop 
module.

This defines the elements priority when stacking elements on the canvas. 
Directly maps to the CSS property.

Also show tooltip on the input to explain what it is for.

To avoid any issues with changing heights.

Also keep track of already given ones.

Stronger then warning.

* Use all style attributes of the unit definition to display
sections
* Remove unnecessary div tag from `SectionComponent`

Remove unnecessary decorator and variable initializers from
`CanvasElementComponent`

Now there is a button at the side that can be used to slide the panels 
in and out.

The extra styling via panelClass needs CSS definition in local project, 
so can not be set by the Service itself but relies on local CSS rules.

This is set implicitly by the sum of section heights.

Add buttons in the dev version of `player-aspect` to work
with exported unit definitions of the `editor-aspect`

Shift the order of style assignments in `updateStyle` method

- Replace in the projects 'editor' and 'player' the selector
'app-root' with 'editor-aspect' or 'player-aspect' and make a
case distinction unnecessary
- Remove definitions of the property 'local' in `environment`
and `angular.json`

Use `build-player-prod` to build a player version of the
aspect-player which can be used in test-center and test-bed.
The player needs exported unit definitions from the
aspect-editor.

This is part of trying to solve the problem of upating styles on already 
rendered components, but still does not work.

player and editor can be served without commenting in
app module and app component. Use `start-editor-local` and
`start-player-local`

THis makes the  components usable in other contexts (player) as well.

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.