these helpers can be used from both the gui and from the command
line interface

the git helpers check github urls and bring back information on
repos from the github api, that will be displayed in the
dashboard

helpers to derive version names for executions are also provided
these version names are formed of the component version and the
component name and are used to reference the component versions
in the file output struture as well as in the gui. Version ids
are used only in the command line user interface and internally,
but are not displayed in the gui

check that the project folder is empty before running prepare
eexecution

this command will be called from the gui and provide info about
the chosen directory folder

the filepicker will be used from the gui to choose the local
project folder

it has been copied from nicegui without any modifications

also remove prepare page as it is not needed

so far ports and port mappings are expected as comma separated
list

pattern matching is used to provide some flexibility regarding the
inputs

add helper to display executions as mairmaid diagrams

remove helper for execution prepare and run as only executions
may be prepared and run via the gui

also add new functions to handle storage of components and
executions in steps

deleting keys in the storage has been refactored
when storage items should be reset the key value pair is deleted
in app.user.storage

there are two reset functions: on keeps only the provided keys
and the other one deletes selected keys

all storage keys are represented by constants so that the storage
retrieval gets less error prone

adapt style and storage handeling

both file contain only one function: therefore it makes sense
to merge these code files

a project folder can be set via the nicegui filepicker example

commandline tools can be started to prepare and run executions
also a command can be started to show the user the tree of the
project folder

the project folder is checked whether it is empty for prepare
execution or matches the tree that is expected to run an
execution

form validation for adding a digital twin is improved so that
only valid entries can enter the database

also show information that is extraced from the github repo
on the component

complete the forms to enter new component versions and the form
to enter new compoents: the component form has two steps, many
values are preset from the github repo

the form to add executions has several steps: one initial step and
then one additional step per component/step; after all steps have
been added the user can see the complete entry with ports and
parameters before submitting to the database