add ci-tooling and config files

[stavros-k]

Supersedes #4

• removed the need of the additional go tool for checking container's health.
• now for each test file in each changed app, a new job will spin. that has some benefits:
  • parallel runs, (no more waiting an hour or even more for apps like minecraft or immich)
  • clean workspace for each test (so we can avoid parsing compose files to identify host paths used to clean them before the next run)

• There are 2 python scripts that are probably hideous to look at. But I figured python would be easier for others to chime in and improve things later.
• I've placed a max of 10 jobs in parallel to avoid hammering github :D.

Currently the ci.py script does 2 modifications during its runtime:

• Copies the top-level library to the app-level based on the app.yaml lib_version field.
• Copies the top-level macros to the app-level.

If we add those 2 steps in a release script we might want to extract them and re-use them

[stavros-k]

Please if anyone got a spare moment and want to take over/refactor this. Please do :)
I'm sure there are a ton of better ways to do all this with python-isms

[Qubad786]

Thanks!