Switch debian to use sysvinit init scripts.

I wrote this because the upstart configs kept getting into an unfortunate state: the docker client managed by upstart would die somehow (without killing the container); this means upstart can no longer stop the container. Since the old container is still running and holding onto network ports, upstart can't start a new container either.

I believe the sysvinit style is better suited to managing Docker containers, since Docker is already managing containers, and stop/start/status map cleanly to various docker commands. Therefore, I've made this patch, which unifies the init scripts between RedHat and Debian.

As added bonuses, this fixes #75 and #100.
a bit of irony: this doesn't always work, because of the behavior that this patch fixes (if upstart has lost track of the container, then `service` can't stop it).

The workaround is to manually `docker stop $container; sudo service docker-$service start` before running puppet. Not sure if there's a good way to automate this, since it's difficult to programmatically tell what container to stop.