Automated testing for applying migrations in a named schema

[laceysanderson]

Issue #145

This PR builds on and is dependant on PR #143. It alters the dockerfile to allow you to name the schema you want chado installed in and creates some automated workflows that do this. This way we can confirm that there is nothing in the migration that is specific to the public schema!

Testing

This really just needs a code review and to confirm the automated testing passes. If you want to be extra thorough or are curious, then you can build the image with a set schema name as follows:

docker build --tag gmod/chado:local \
  --file docker/Dockerfile \
  --build-arg SCHEMA_NAME="teacup" ./
docker run -it --rm --volume=$(pwd):/Chado gmod/chado:local

This will install chado into a schema named teacup. You can use psql -U postgres -h localhost -d chado with the password chadotest to look at the schema. Specifically, \dt public.* should only have a flyway table and \dt teacup.* should list out the whole chado schema + a flyway migrations table.