Low: remote: Downgrade proxy relay failure to a debug msg

We don't want to see these errors if the remote client
disconnects before the response comes in.
Low: cts: Verify libvirtd is up before running pacemaker remote tests.
Low: cts: Don't remove lxc config files during pcmk remote tests
Low: cts: Distribute lxc config files to all nodes in cluster so monitors do not fail
Merge pull request #347 from davidvossel/pcmk_remote_cts

more pcmk remote and cts fixes
Feature: cib: Support XML comments in diffs
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
Merge pull request #349 from gao-yan/xml-diff-comment

Feature: cib: Support XML comments in diffs
Merge pull request #348 from davidvossel/baremetal_remote

Initial baremetal remote-node support
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