Use separate pid files for Pacemaker OCF

W/o this change, improved pacemaker provider
would not differ OS-aware service pid file from
its own one. That would make impossible to
disable OS-aware services inside pcs provider.

The solution is to separate OS-aware layer from
pacemaker OCF one for pid/run/lock files (we use
only pid files in OCF scripts):

* Unify $OCF_RESKEY_pid_default definitions with
  $HA_RSCTMP and "$__SCRIPT_NAME" varaibles
* Add separate pid directories for resources managed
  by pacemaker OCF ($HA_RSCTMP/$__SCRIPT_NAME/)
  and keep pid files there to distinguish them from
  OS-aware ones.
* While $HA_RSCTMP is owned by root, chown resources'
  subdirectories $__SCRIPT_NAME to
  $OCF_RESKEY_user to grant daemons
  write access for their pid files as well.
* For status actions of OCF scripts, add safe creation
  and chowning of aforementioned pid directories
* Add missing user/group checks for rabbitmq ocf
* Add debug for pid file related actoins
* Make empty pidfile checks
* Fix pidfile creation on start action of neutron
  agents OCF
* Fix pidfile deletion on stop action for mysql OCF
* Add missing pid file checks for rabbitmq status
  and update report not running conditions

DocImpact
Related blueprint pacemaker-improvements

Change-Id: I7f50e32ced83af8f32fd7907cb5fc723055da121
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>