Fix: tools: Fixes formatting of remote-nodes in crm_mon and crm_simulate
Low: crmd: Cache baremetal remote-nodes
Low: pengine: Strip 'remote-' prefix from baremetal remote-node attributes so attributes can be consistent between baremetal and resource remote-nodes
High: pengine: Allow fencing of baremetal remote nodes

Baremetal nodes are now fenced in the same way cluster nodes
are fenced.  If the baremetal node has not status section, it
will be fenced on startup. If the baremetal node is down but
there are resources that didn't shutdown, the node will be fenced.
If a resource failure on the baremetal node should result in
the node being fenced on failure, then the baremetal node will
get fenced.
High: crmd: Remote-node fencing glue
High: pengine: Probe resources on baremetal remote-nodes
Low: pengine: Updates to regression tests to reflect probing remote-nodes
Low: crmd: Clear remote-node status AFTER start completes, not before.
Low: pengine: Refactor how we detect remote-nodes to use helper functions
Low: pengine: Initial baremetal remote-node PE regression tests
Low: cts: Baremetal pcmk remote cts test
Low: crmd: Populate remote peer cache when building new cib
Fix: pengine: Properly shutdown orphaned remote connection resources
Low: pengine: Orphaned remote resources pengine test
Merge pull request #348 from davidvossel/baremetal_remote

Initial baremetal remote-node support