RFC 235: Do not mush data together in the server deployment

Created by: efritz

Right now the code intel and frontend database is the same in dev (on purpose) and in the server environment (incidental). Because people actually use the server environment and would need an upgrade path to compose or kubernetes, we need to ensure that we don't allow any real (non-local/non-dev) instance from using the same database.

We should update the server startup to ensure that are two databases (in the same postgres) container, and that it works with fresh and existing postgres data.