Tobias Kiertscher

Depends on #90

Internal PlugIn architecture via aspect-oriented interfaces. Possible aspects: - creation/initialization - dependency download - build - watch - edit - clean - release - publish

Commands from CLI: `project`, `prj`, `p` - [ ] ... `new`, `n` `` `[args*]` - [ ] ... `backup`, `a` `` - [ ] ... `dependencies`, `deps`, `d` `` -...

Plug-in interface need to be worked out to define the possible user tasks at the Dashboard and the CLI.

Most importantly the checkout of existing projects should be imlemented, because it generates the biggest benefit for Bench as a prepared dev-environment.

* Default editor for the whole Bench environment * Default editor for an individual project

Added config properties `TextEditorApp`, `MarkdownEditorApp` in 59c5e3d1ac92c106677cd3a204dbf437197688a0.

Removed config property `MarkdownEditorApp` in 48b4e986153a7ff290064798fd44573c9971c4fa.

Started implementing build pipeline on private GitLab CI.

Every package can have multiple components (`bin`, `man`, `doc`, `dev`, ...). An app property `Components` should list the required packages. The default value of `Components` should be `bin`.