qa trivial PMDA - maintain pmcd configuration state

QA tests that install/remove PMDAs should leave the pmcd
configuration in the same state they find it.
qa/365 - take better care of white space in the filtering
qa/348 - kvm PMDA & maintain pmcd configuration state

QA tests that install/remove PMDAs should leave the pmcd
configuration in the same state they find it.
libpcp_fault/GNUmakefile - needs to know about secure socket changes

Needed conditional source file inclusion just like libpcp.
qa/012,514,520 - variant output is for PCP 3.7.2

Previously conditional for 3.7.1, but after official 3.7.1
release.
qa/712,713,714 - chmod to be executable
qa/287 - slightly different floating point precision for x86_64
libpcp/nss_connect.c - add some -Dcontext diags
Merge branch 'dev' of git://oss.sgi.com/pcp/pcp into dev
qa/008 - fix disk non-determinism for host bozo
qa/024 - filter out __pmConnect diag added in PCP 3.7.2
qa/200 - handle new __pmConnect diag added in PCP 3.7.2
qa/273 - filter out __pmConnect diag added in PCP 3.7.2
Revert "qa/287 - slightly different floating point precision for x86_64"

This reverts commit 8704c97674c69da4ac7704b61dd7978d5a6fb4e3.
qa/297 - filter out __pmConnect diag added in PCP 3.7.2
qa/455 - rsyslog pmda testing

A couple of changes needed here:
a) maintain pmcd configuration state ... if the PMDA is installed
   before this test runs, make sure it is installed after the test
   has been run, else if the PMDA is NOT installed before this
   this test runs, make sure it is NOT installed after the test
   has been run
b) add a small amount of checking for the named pipe creation
   ($PCP_LOG_DIR/rsyslog/stats) to avoid a race between the Install
   and the QA test that can leave the QA test hanging on the write
   to the named pipe.
qa/439 - filter refinement

Treat "TCP connection reset by peer" as equivalent to "Connection refused"
for this test.
qa/group - test 193 belongs in the pdu group
Diagnostics - add DBG_TRACE_DESPERATE support

One level of additional verbosity control in the diagnostics.

Set from the command line with one or more flags, e.g -D pdu,desperate
and execution is guarded by a predictate like
    if ((pmDebug & DBG_TRACE_PDU) && (pmDebug & DBG_TRACE_DESPERATE))

The intention is that only the desperate developer would (a) add
diagnositics under the conjuncted DBG_TRACE_DESPERATE control,
(b) be interested in the output from these diagnostics.

For example uses in libpcp, see the subsequent commits to pdu.c and ipc.c.
libpcp/ipc.c - hide noisy diagnostic behind DBG_TRACE_DESPERATE

The DBG_TRACE_CONTEXT diagnostic
    __pmDataIPC: fd=<n>, data=<addr>(sz=<k>)
is generated a _lot_, and is not all that helpful amongst the other
-Dcontext diagnostics, so hide this one behind the (new) conjuncted
DBG_TRACE_DESPERATE flag.

-Dcontext,desperate will make it appear again if needed.