use latest_release path in update_crontab

This should fix the timeout issue encountered by some in 0.8.1. This reverts to using latest_release as the path for update_crontab cap tasks. This change was inadvertent to begin with, so reverting it back is a good thing.

This addresses issue #288, but doesn't fully fix it.