[META] Travis CI Integration for automated testing

Now that we have working docker images and a small number of behat tests, we can add .travis.yml files to all the sub projects for free automated testing on travis.

• Behat tests and .travis.yml files: https://github.com/aegir-project/tests
• Dockerfiles: https://github.com/aegir-project/dockerfiles and https://hub.docker.com/r/aegir/hostmaster/
• Development environment: https://github.com/aegir-project/development

This is also the easiest way to let users contribute: They visit github, find a file they want to edit, click "Edit" and select" create a fork, new branch, and new pull request.

Travis will automatically kick off a build for all newly submitted pull requests.

The nice part about this is that github repo can just be a mirror, but we can still let people submit PRs there, and manually push them to the canonical upstream (either drupal.org or gitlab).

This patch might not be 100% ready, but that's why it's in a pull request on github.

I have to test out a pull request from a forked repo.

Once this is done we write a modified travis yml for provision and hosting repos, then start writing more in depth tests!

GitHub Pull Request: https://github.com/aegir-project/hostmaster/pull/1
Pull Request Patch: https://patch-diff.githubusercontent.com/raw/aegir-project/hostmaster/pu...

Next Steps

1. Add to hosting: https://github.com/aegir-project/hosting/pull/1
2. Add to provision: https://github.com/aegir-project/provision/pull/2
3. Add example yml files for contrib modules:
4. Write more tests. Converting the test drush command to Behat will not be very difficult, however writing up behat tests has already exposed bugs, so it won't be a trivial process. See https://github.com/aegir-project/tests/pull/1
5. Write up a page in the documentation about the new automated testing system. Create a table for test result badges for all repositories.
6. Write up a page in the documentation about the development environment and how to contribute with Pull Requests.
7. Promote it with a blog post on our new website!