Add an option to disable monit configuration

[kraft001]

Solves #181
Allows a user to skip the monit configuration step if monit was already configured on the server

[Tensho]

This controversy to #193. IMO, sidekiq monit conf MUST be re-upload on every deploy automatically. Suppose you changed some sidekiq options that should be reflected in monit start command inside monit config file, e.g. sidekiq_concurrency or sidekiq_logfile.

[kraft001]

@Tensho I completely agree with your point, it's valid when a developer has access to monit config files.
But in our case monit is managed by sysadmins who built their own Puppet scripts, and developers cannot change those scripts. More options don't hurt but help developers to handle such cases.

[Tensho]

@kraft001 ah, I see what you mean. In such a case it makes sense, even though sysops should reflect (sync) any configuration changes developers introduced by hand in this case. Does capistrano-unicorn or capistrano-puma have the similar configuration option?

[kraft001]

@Tensho Neither of the mentioned gems has such an option

[Tensho]

@kraft001 🤔 Maybe conventionally deploy should be run from Puppet system either... I don't see any significant drawbacks incurring this config option. Could you please rebase the branch?

@seuros, What do you think on the subject?