disable database service on stage/prod

What does this MR do?

Introduce a way to disable services on stage/prod

Why is this MR needed?

Because we already use a database outside of the VM. Other services like object-storage, mqtt-broker could potentially also be external.

How to test this MR?

1. run time.IO with the database service
   • nothing to see here
   • business as usual
2. run time.IO without the database service
   • cp docker-compose.override.prod.yml docker-compose.override.yml
   • either
     • set up local database connection outside of tsm-orchestration
     • set .env to use this database connection
       • e.g. replace =database with =172.17.0.1, the bridge network gateway
     • run time.IO - everything works well 👍
   • or
     • see flyway fail, as it can not connect to db
     • let's test it on stage

⚠️

Do not change the auto-generated Merge commit message or Squash commit message, otherwise the release pipeline fails!