Add DRBD support for HA

Co-Authored-By: Vincent Untz <vuntz@suse.com>
Split the colocation / order constraints

Since we first create the filesystem-related pacemaker resources and
then do some actions on the filesystem before creating the other
pacemaker resources, we need to have the constraints in place forthe
filesystem before we do the actions on the filesystem.
WORKAROUND: cleanup the resources
Always use a pacemaker group

The colocation / order constraints are actually only really needed
between the master-slave and the filesystem, and since we split that
part out, we can then simply use a group for the rest.
Stop monitoring postgresql through the IP address and with a password

The password is not correct the first time, which can result in some
issues.
Use inf for score, not INFINITY

The result is the same for crm, but our pacemaker cookbook cannot
properly compare the values when using INFINITY.
Update for new crowbar_pacemaker_drbd LWRP
Make sure the constraints that we create are using the right primitive

We initially create the constraints with the fs primitive, but as soon
as we create the group, pacemaker (being clever) changes the constraint
to be about the group instead of the fs primitive.

As we do not want to change Make sure the constraints that we create are
using the right primitive

We initially create the constraints with the fs primitive, but as soon
as we create the group, pacemaker (being clever) changes the constraint
to be about the group instead of the fs primitive.

As we do not want to change the constraints again on the next chef run,
we need to handle that case.the constraints again on the next chef run,
we need to handle that case.