fix(scheduler/coreos): skip announcer containers for start, stop, destroy

With #1269 we stopped creating announce containers except for web and cmd
types, but we still attempt to perform actions on them for start, stop,
and destroy. This commit adds logic to wrap all of these scheduler actions
in a conditional which skips (and logs) announce operations.

TESTING: rebuild the controller
```console
$ make -C controller stop build start
```

Then, deploy an application which has either a cmd or web proctype, as
well as a non-standard type. I modified the Procfile for our
example-ruby-sinatra like so:

```
web: bundle exec ruby web.rb -p ${PORT:-5000}
clock: echo flava flavvvvvvv
```

Scale the app, start/stop processes, etc. You should see successful
operations for both, and note that the clock type has no announce
containers. The output of ```deis ps``` should always show them
as being up:

```
=== exotic-icehouse Processes

--- web:
web.1 up (v3)
web.2 up (v3)
web.3 up (v3)

--- clock:
clock.1 up (v3)
clock.2 up (v3)
clock.3 up (v3)
```

fixes #1273
closes #1275
Merge pull request #1279 from deis/1275_skip_announcers

fix(scheduler/coreos): skip announcer containers for start, stop, destroy
feat(*): move data containers into new unit files

Moving these containers into their own data files
sets the stage for locking data containers to specific
machines. This also enables us to stop Postgres cleanly on
the database-data container.

closes #638
fix(controller): format command before creating container

The self._command_announceable() check was called inline with code
that formatted the container's command, so no announcer would be
created since the command showed up as "start {c_type}" literally.
The _command property is only referenced in this code.
fix(*): schedule data containers to specific machines

Currently, whenever database, logger, registry, or builder are rescheduled
by fleet, their data container is left on the original machine. The effect
for the user is that they lose their data! This commit schedules data containers
to a preselected machine. If that machine goes down, the underlying service will
go down, but this is preferred to scheduling it on another host that won't have
the data.

Note that this is an interim fix - stateful data should be stored off-host.

closes #1038
test(controller): add regression test for "start {c_type}" bug
Merge pull request #1107 from deis/1038-static_data_containers

fix(*): schedule data containers to specific machines
Merge pull request #1285 from deis/hotfix-app-announcers

fix(controller): format command before creating container
chore(tests): update vendored Docker cli code to v1.1.1
fix(tests): use `docker run --rm` instead of explicitly removing containers
fix(Makefile): only install data containers if they don't exist

Since we are scheduling data containers to specific machines (and
the machine we choose is random each time), we want to be careful
about when we regenerate and resubmit these units.

This commit makes `make install` (and thus `make run`) safe to
run multiple times again since they will now only submit data containers if they don't
already exist.

TESTING: run `make install` multiple times and ensure the units are there when they should
be, and not resubmitted otherwise
```console
$ make uninstall
```
```console
$ make install
Job deis-router.1.service loaded on e35efc85.../172.17.8.100
Job deis-builder-data.service loaded on e35efc85.../172.17.8.100
Job deis-database-data.service loaded on e35efc85.../172.17.8.100
Job deis-logger-data.service loaded on e35efc85.../172.17.8.100
Job deis-registry-data.service loaded on e35efc85.../172.17.8.100
fleetctl --strict-host-key-checking=false load registry/systemd/deis-registry.service logger/systemd/deis-logger.service cache/systemd/deis-cache.service database/systemd/deis-database.service
Job deis-logger.service loaded on e35efc85.../172.17.8.100
Job deis-registry.service loaded on e35efc85.../172.17.8.100
Job deis-cache.service loaded on e35efc85.../172.17.8.100
Job deis-database.service loaded on e35efc85.../172.17.8.100
fleetctl --strict-host-key-checking=false load controller/systemd/*.service
Job deis-controller.service loaded on e35efc85.../172.17.8.100
fleetctl --strict-host-key-checking=false load builder/systemd/*.service
Job deis-builder.service loaded on e35efc85.../172.17.8.100
```
```console
$ make install
deis-builder-data.service already loaded. Skipping...
deis-database-data.service already loaded. Skipping...
deis-logger-data.service already loaded. Skipping...
deis-registry-data.service already loaded. Skipping...
fleetctl --strict-host-key-checking=false load registry/systemd/deis-registry.service logger/systemd/deis-logger.service cache/systemd/deis-cache.service database/systemd/deis-database.service
fleetctl --strict-host-key-checking=false load controller/systemd/*.service
fleetctl --strict-host-key-checking=false load builder/systemd/*.service
```
Merge pull request #1291 from deis/readable_data_containers

fix(Makefile): only install data containers if they don't exist
fix(tests): report errors from `docker pull` on main goroutine

See http://golang.org/pkg/testing/#T.FailNow
Merge pull request #1268 from deis/component-tests-fixes

fix(tests): improve reliability and error reporting for component tests
chore(controller): update Django to 1.6.5 security release

https://www.djangoproject.com/weblog/2014/may/14/security-releases-issued/
chore(controller): update South to 1.0 final release

http://south.readthedocs.org/en/latest/releasenotes/1.0.html