Restart sidekiq-cluster when relevant changes occur
If any Rails-related changes or database migrations occur, Sidekiq was being restarted automatically, but sidekiq-cluster was not. We fix this by making sidekiq-cluster a dependent service.
Closes #4020 (closed)