Fixes for rabbit OCF logic

W/o this fix,
* forget_cluster_node command could take a lot of
  the time (and even out of the time given to post-stop notify event)
  if rabbit node is under heavy load.
* It is also possible that all
  rabbitmq resources could persist as a slaves and there won't be
  any master elected.
* Sometimes, join_cluster could take quite a long of a time. If it exceeded,
  the node will enter into join-wait-reset loop for ever.

The solution includes:
* Disconnect the node being unjoined forcibly from
  the every node issuing the forget action. That would make the forget
  action an instant and would ensure the node will be unjoined and
  reset w/o any issues.
* Increase action start timeout even more and increase minimal value
  for command timeout as well.
* Add info messages about timeouts given for commands execution
* Fix missing OCF_FAILED_MASTER status processing for events and actions
* Fix promote/demote/notify actions - return OCF_FAILED_MASTER then required
* Fix reset_mnesia() procedure and logging prefixes for it
* Replace detached stop_app call to timeout wrapper in stop_rmq_server_app()
  and stop_server_process(). Del del OCF_RESKEY_shutdown_time (unneeded).
* Fix exit code for start_rmq_server_app()
* Fix missing return for jjj_join
* Fix my_host return codes to differ from OCF_ERR_GENERIC
* Fix missing local declarations rc var
* Fix missing rc checks for stop_rmq_server_app() and some other functions
* Add some missing ocf_run wrappers
* Fix shutdown/startup logs redirection

Related-bug: #1396946

Change-Id: I951825badb712c5575d469403cf65bf26713aff0
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
Merge "Fixes for rabbit OCF logic"