Consider using docker stack for development / testing deployments

[seanshahkarami]

I've had an extremely good experience with using the docker stack features for doing a local development / testing deployment on my own laptop. I've been tracking that experiment here: https://github.com/seanshahkarami/beehive-stack

We should strongly consider transitioning the way beehive is deployed to use something like this. A few benefits are:

• There's a single file describing which containers are deployed, with what settings, how they're related, what volumes they use, etc.
• A single command can create and destroy the entire deployment.
• Services are managed by docker, so we won't need both docker and systemd configurations.
• It's easy to run locally. I already use this on my laptop. Imagine how useful that would have been for summer students...
• Future / reach benefits: Plays nice with docker swarms...I've already been able to run services across a desktop machine clustered to beehive2. If we're not moving to something like AWS, we should measure the performance of this. This would help us add hardware fault tolerance, redundancy and help us scale horizontally.

[seanshahkarami]

If we don't end up transitioning to AWS ever, something like this could really help development. We need to get out of this stasis mode where iterating on beehive is difficult and "scary".

[seanshahkarami]

After all the clean up, I'm already starting to use this for local development, so I'm choosing to close this issue for now.