Allow a retry when creating a VIP primitive in pacemaker_vip_primitive

As nodes will race to initially create the VIP primitive, they will
likely hit some failure because only one can obviously create it. Once
it's created, there's no issue as there's a check for existence.
Add a PacemakerHelper module with various helpers
Add a haproxy cookbook

It is not based on the upstream one, which would require too many changes.
Add a crowbar-pacemaker wrapper cookbook and switch to it

This cookbooks wraps all the use of upstream cookbooks, in order to
allow proper crowbar integration, as well as integration between two
independent cookbooks.

Concretely, we provide an easy way to install haproxy on pacemaker
clusters.

Note that we always install haproxy on cluster nodes.If we were not doing this,
then some nodes would not have it installed when the resource is first declared
and these nodes will have this error:
    warning: services_os_action_execute: Cannot execute '/etc/init.d/haproxy': No such file or directory (2)
The error is fixable with "crm resource refresh", but we might as well just
install the package.