In God configuration, put resque-related watches (resque-worker, resque-scheduler) and the redis-server watch in different groups.

This is a first step towards only restarting resque watches when deploying the app, and leaving redis-server running all the time.

If a configuration change requires a restart of the redis server it can be done manually, of course. But it should not happen often. Resque workers however have to be restarted on each deploy, so that any changes in code are picked up (resque reads ruby code when started and does not read it again unless restarted).
When deploying the app with capistrano, restart only resque workers and resque-schedule. Do not restart redis-server.

Also with this commit, god itself is not restarted when deploying the app. This means that:

- if the redis config changes, redis will have to be manually restarted
- if the god config changes, god will have to be manually restarted
When resque workers are stopped by God, they wait up to 5 minutes for child processes (which do the actual work) to finish before forcefully killing them.

Before this commit, this grace period was 10 seconds. I think 5 minutes is enough for even a long-running job to finish (and I want them to finish before restarting resque, if possible).