Publish Docker images publicly

[applejag]

Based on RFC-0011: quay.io

Docker images are currently stored in our internal docker repo. We want these to be publicly available.

We shall host them over at https://quay.io
Both are free for open source repos. Quay.io includes RedHat's Clair that gives industry leading security scanning.

Todo

1. Register account on quay.io using wharf@iver.com with the username iver-wharf (same as on GitHub)
2. Setup our build pipeline to deploy images to quay.io
3. Optionally add a badge in the README.md (ex: https://quay.io/repository/iver-wharf/wharf-api/status)
4. Update docs on how to get and use docker images
5. Update docker-compose.yml in iver-wharf/wharf-docker-compose to reference the new image names so you don't need to build them locally, but still can

Conflicts

Certificates! Oh the joy!

We need a better way to import our internal self-signed CAs than our current procedure where we're embedding them into the images. But this deserves a different GitHub issue and nothing we should have to worry about here. It can be looked into in #44

[applejag]

Tried building the images via quay.io as a test, and there's this silly issue here:

https://quay.io/repository/iver-wharf/wharf-provider-github/build/12709729-520c-4627-a5a0-79a6b7e60b4e

The base image in that Dockerfile is docker.io/golang:1.13.4, i.e. this: https://hub.docker.com/_/golang

We ultimatetly want to rely on Wharf to build these things, but I'm still rumped that it didn't work :(

Until we get Wharf up and running for GitHub & quay.io integration, we'll resort to just manually building and pushing it locally

[applejag]

Image has been pushed. They are all available over at:

docker pull quay.io/iver-wharf/wharf-api:v4.0.0
docker pull quay.io/iver-wharf/wharf-web:v1.2.0
docker pull quay.io/iver-wharf/wharf-provider-github:v1.1.1
docker pull quay.io/iver-wharf/wharf-provider-gitlab:v1.1.1
docker pull quay.io/iver-wharf/wharf-provider-azuredevops:v1.1.1