- Replace asynchronous child processes with synchronous processes
- Add shortcuts to package.json

Move label creation to ElementFactory.

No way has been found to have an abstract static method for 
OptionElement's label generation, therefore silence the linter.
Same for getElementComponent.

#298

This reverts commit da09ac1e.

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.

- upgrade @ngx-translate/core
- upgrade rxjs
- upgrade testcafe

- run npm update

Build and deploy script are written in bash for now as the syntax is
far easier and cleaner. Might be changed in the future as this requires
a Linux environment with bash available.

Deployment happens as version 9.9.9, because Teststudio does not accept
players and editors without semantic versioning.

The Dockerfile is the image used for building and deploying the app.

The package karma-spec-reporter is to show more info about run tests on 
the console.

Numbers on the test files refers to the version (2 digits for minor; 
patch number ignored).

New name: richTextOptions

Unit definition version has been raised accordingly.

#200

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

becomes

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

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

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