qa/518:

It was observed that the $sudo pmie invocation didn't always
receive the closing signal at this test case, leading it to
hang.  Now we kill it harder, both by pid and later by name.
qa/518: stretch timing to run more reliably

This test case involves a race between pmie running rules a certain
number of times, and a separate task waiting (by time) to match the
results via /usr/bin/pcp.  It was observed as flakey, not always
winning the race.  This version stretches the pmie time and fine-tunes
the waiting interval to give the race a larger (multi-second) window
for success.
qa/985 - remove ./dmcache.log before exit
qa/553 - remove ./gluster.log before exit
qa/763 - remove domain.h.perl and pmns.perl before exit
qa/841 - remove domain.h.python before exit
qa/832: remove pmns before exit
qa/518: better checking for the expected number of rule evaluations

Change timing to revert to older duration (4sec, not 12sec).
Avoid use of pmsignal all together, so pmie exit is guaranteed.
Tolerate small differences in the number of rule evaluations.
pcp(1): add missing sort for -P output

With multiple pmie's running, pcp -P could fail because the inputs
to one of the (many) join commands is not not sorted.

Found in the rework of qa/518.
pmcd: additional diagnostics in the area of user/group authorisation
qa/944: better handling of multiple users being in the same default group

For example on grundy, need to handle case when the target is _not_ first
in the list, ... so filter
 12(games),1000(kenj),1001(trev)
to produce
 GROUPID(GROUPNAME),...
not
 12(games), GROUPID(GROUPNAME),...
build: update packaging and project forward for next release date

The rpm spec files are cleaned a little to reduce dependencies on
a number of not-actually-pre-requisite rpms.
Merge branch 'dev' of git://git.pcp.io/kenj/pcp into dev