Fix: remote: Handle request/response ipc proxy correctly

We now preserve whether a proxied ipc server message is intended
for the event or response channel without trying to guess based
upon the way we expect most server implementations to behave.

This fixes an issue where pacemaker_remote is unable to manage
master/slave resources because proxy communication with the attrd
is unreliable.
Fix: pengine: properly handle fencing of container remote-nodes when the container is orphaned
Low: cts: reference ping resource by clone id in location constraints
Low: cts: fix how lxc_autogen handles placing resources on remote nodes
High: remote: clear remote-node status correctly

Previously container remote-nodes had their status cleared
after the connection resource started. If the transition is aborted
between the container starting and the connection resource starting
for a remote-node, the previous status entry causes it to look like
the container is up with active resources while the connection resource
is down... This causes the container to be fenced.

To avoid this situation, container remote-nodes initialize their
status sections right as the container is up, even if the actual
connection resource has not started.
Low: pengine: regression test updates for recent container fixes
Merge pull request #536 from davidvossel/cts-lxc-updates

pacemaker remote related fixes