Build: spec: ocf:pacemaker:controld not eligible for Pacemaker+CMAN

CMAN initscript (presumably with a uniform behavior across the nodes)
achieves for DLM (GFS) what globally unique clones of controld will, and
this supervision spans beyond Pacemaker's lifetime (initiated prior to
its start and finalized after its stop), so that controld agent entering
already supervised space might be without effect or downright harmful.
Furthermore there's quite a complex intertwining with distributed
storage layer, so it's best to ensure controld cannot be configured,
not even accidentally or because of following tutorials for a different
Pacemaker setup (vast number of setups is actually not a CMAN variant).

See also:
https://bugzilla.redhat.com/1312040#Pacemaker-used-with-CMAN-should-not-ship-ocf-pacemaker-controld