Rethink orchestrated docker boot

[Taucher2003]

Currently, the orchestrated docker boot first starts a postgres database container, connects to the docker network and then boots the rails server.

This worked fine for a while, but now there is a need to get more configuration done. For example generating and storing database encryption keys or the secret key base.

Ideally this should be re-built with a configurator container that does the configuration and then starts new containers with the corresponding environment variables instead of booting the app in itself.

[Taucher2003]

We are going to fully remove the orchestrator and orchestrate on the package layer (docker-compose, helm-chart, ...)

For the configuration, we switch to a configuration file and application settings. The options that can be configured with ApplicationSettings can also be overridden by the configuration file

[Taucher2003]

The orchestrator has been fully removed from the codebase.

Whats left is to implement the package layer. That however should be developed in a separate project.