offer config via a seperate inifile
use new repo in parent folder, fix paths
store runtime config locally
don't store the filename in the json
eliminate standard_nodetypes from js
automize node-types:

offer to customize shape, provide reasonable default.
create "create-node-menu" dynamically
generalize node menu
remove unused nodetypes
Merge branch 'master' into nodenets_are_code
allow for definition of own nodetypes

current convention is to look for "nodetypes.json" in the given data_directory from the configfile
scan for custom nodefunctions in custom resource path
remove legacy nodetype definition from testdata
preliminary fix for test setup
set resource_path back to default
standard nodetypes prevail
fix missing filename when creating default world
fix some linter warnings on the way
distinguish standard nodetypes and native modules
treat Native Modules differently in extra sub-menu

We'll probably need to introduce a scrolling menu or dialog on the long hand.
If there we have more than 10~15 Native Modules, the current solution will get messy