fix for issue 3

- it doesn’t depend on key retry_count to schedule or not schedule
anymore, we now set a key named rq:schdlr, which indicates that current
worker is the one that should schedule next worker, this key is removed
from current worker msg and set the next one
- it now cancels failed workers