use the same ENV => INI => default strategy for SQL_HOST in php that we have had for all config vars in py services

troubleshooting config via docker-compose volume (new logic for debug messages, run.sh reads ini file, but shell env vars get priority over config vars)

merged the two python services to run them together via run.sh and adapted the docs... this new version takes almost all functionalities from david chavalarias's and samuel castillo's work, cleaned up and integrated with the new registration service and a standard docker+nginx packaging for deployment

tidy up php scripts: 10 are used via include (=> moved to lib dir) while 5 are used for front end (search_* and print_*) => stay

git-subtree-dir: static/tinawebJS
git-subtree-split: d5aa12279a375de94420da49fa08ba5dc1f5c784

move all legacy js, css and img into static for faster serving (todo same with tinawebJS subtree and explorerlibs)

move backend into new services folder for later merge with db_to_tina_api from moma/legacy_php_comex/commit/4d19264a + add stubs for future user login and text normalization classes

update readme + add authors + move comex_install to a services dir for future merge with the regcomex service

replaced tinawebJS submodule by a subtree with a dedicated branch pointing to https://github.com/moma/tinawebJS/tree/comex_wip

git-subtree-dir: tinawebJS
git-subtree-split: 86a6f0c88f988976bca0c9dd3b081105bf9fc482