chore(contrib/*): update to CoreOS 324.1.0

Double-check the IDs:
EC2: https://coreos.com/docs/running-coreos/cloud-providers/ec2/
Rackspace: https://coreos.com/docs/running-coreos/cloud-providers/rackspace/
fix(Makefile): update to work with fleetctl 0.3.2
fix(data-containers): change test command to "inspect"

We used "docker start" to test for the existence of data containers,
but this can fail after the container has run, and cause the || clause
also to fail with "name in use".
fix(controller): use new `fleetctl` semantics

Fleetctl 0.3.2 by default will test for a unit's goal status 10 times,
once every tenth of a second, before failing. This is not generous
enough, so on starting services we do it async with `-no-block` and
then poll for goal status, and on stopping we wait 60 seconds.
fix(controller): watch fifth column for state

fleetctl v0.3.4 introduced a fifth column, so we need to update
the location of the state column.
docs(contrib/rackspace): document manual update for CoreOS

Since the Rackspace images are updated infrequently, we still use
CoreOS 317.0.0 images on Rackspace. This commit details the workaround
to manually update CoreOS to the latest release from the channel.
Merge pull request #1019 from deis/coreos-317.0.0

chore(contrib/*): update CoreOS to 324.1.0
fix(Makefile): enable targets to work for non-Vagrant

Adds DEIS_HOSTS, which is set automatically or can be overridden
for non-Vagrant platforms. This is used by ssh_all to determine
which hosts to SSH into - previously, we used `vagrant ssh`,
which obviously only works on Vagrant.

This also updates all the Makefiles to use fleet as appropriate,
and to pull / build / etc. on all DEIS_HOSTS.

TESTING: try the various make commands on Vagrant and Rackspace/EC2

replaces #998
closes #811
Merge pull request #1026 from deis/deis_hosts

fix(Makefile): enable targets to work for non-Vagrant
feat(router): route deis.domain to controller

Forwards requests to deis.domain to the controller.

TESTING: rebuild the router and controller with this change:

    $ make -C router build restart
    $ make -C controller build restart

Test that deis.domain routes to the controller and that other
requests to the domain route to the app. Also, send several requests
to the API and be sure that nothing broke related to auth because
of the proxying of requests.

The integration tests were updated to test the controller and the app
routing, so you can also `cd test && bundle exec rake`.

Also, try creating an app with the name of 'deis' - it should be
rejected.

replaces #974
part of #535
test(controller): check for appname = deis
fix(travis): add dummy FLEETCTL_TUNNEL envvar

This fixes the errors we are seeing on TravisCI.

replaces #1045
Merge pull request #1048 from deis/fix-travis

fix(travis): add dummy FLEETCTL_TUNNEL envvar
fix(controller): change timeout for docker container template

change the default timeout for the docker container template to 20m
fix(router): restore check_cmd and grep nginx.conf

We were having issues with router coming up due to "<no value>"
being templated into /etc/nginx/nginx.conf. Thanks @gabrtv.
Merge pull request #1011 from deis/controller-behind-router

feat(router): route deis.domain to controller
docs(UPGRADING.md): add upgrade documentation

Adds documentation outlining two upgrade workflows for Deis clusters.

closes #1012
Merge pull request #1031 from deis/upgrading_deis

docs(UPGRADING.md): add upgrade documentation
docs(configure-dns): fix typo

There was a typo preventing the bulleted list from rendering properly.
fix(docker): always use ":latest" tag in docker pull

Now that the Docker Index allows tagged builds directly from GitHub
project tags, we will version Deis components properly as
deis/controller:v0.9.0 rather than deisreleases/controller-v0.9.0.
At that point, doing a plain "docker pull deis/controller" will pull
down all tagged images when we only wanted one, so this change
prevents users from wasting more time on already slow download operations.
Being explicit about the docker image tag also facilitates our
release process.