WIP: add pacemaker constraints needed for reboots

This is still an early WIP.

An additional enhancement has been added where pacemaker IP resources are named like:

     ip-horizon-adm-192.168.201.95      (ocf::heartbeat:IPaddr2):       Started pcmk-c1a1
     ip-horizon-priv-192.168.201.94     (ocf::heartbeat:IPaddr2):       Started pcmk-c1a2
     ip-horizon-pub-192.168.7.100       (ocf::heartbeat:IPaddr2):       Started pcmk-c1a2

for sanity (e.g., instead of just ip-1.2.3.4).  I thought about removing the actual IP address from the resource name altogether (e.g. ip-horizon-pub) but A) I'm not sure this is really a huge win because it is nice seeing the IP in pcs status and B) a pretty large refactor to ha-all-in-one-util.bash would be needed.

The idea right now is to use quickstack::pacemaker::constraint::haproxy_vips as the way to define constraints between haproxy and the vips (pretty much every vip has a constraint on haproxy, so following the pattern we already use for vips makes sense here).  All other non-vip inter-service ordering constraints will live in quickstack::pacemaker::constraints.
When I was working on the define for resource::generic, I was unsure whether to use $name or $title.  According to the puppet docs, when in doubt, use $title.  If you have a reason to use $name, then by all means do so, just thought I would mention it.