qa: avoid test 666 pmmgr/valgrind RHEL QE failures
qa: avoid test 666 pmmgr/valgrind RHEL QE failures

> ==11675== 28 bytes in 1 blocks are possibly lost in loss record 8 of 21
> ==11675==    by 0x186BFB: main (pmmgr.cxx:1628)
>    fun:_ZNSs12_S_constructIPKcEEPcT_S3_RKSaIcESt20forward_iterator_tag
>    fun:main

> ==11675== 38 bytes in 1 blocks are possibly lost in loss record 9 of 21
> ==11675==    by 0x19334B: pmmgr_job_spec::compute_hostid(std::string const&) const (pmmgr.cxx:314)
>    fun:_ZNK14pmmgr_job_spec14compute_hostidERKSs
>    fun:pmmgr_pmcd_search_thread
>    fun:_ZNK14pmmgr_job_spec11parallel_doEiPFPvS0_ES0_
>    fun:_ZN14pmmgr_job_spec4pollEv

> ==11675== 39 bytes in 1 blocks are possibly lost in loss record 10 of 21
> ==11675==    by 0x186B9F: main (pmmgr.cxx:1622)
> ==11675==    by 0x195CD3: append (basic_string.h:1009)

Each allocation sites identified is for an object whose
lifetime is associated with a stack frame and cannot leak.

For valgrind to report this way is more likely to be a
valgrind bug or some weird side-effect of shutdown due
to a external kill -9 (?) from the test case driver.

Resolves Red Hat BZ #1343319.

adfernandes/pcp,adfernandes/pcp,adfernandes/pcp,adfernandes/pcp,adfernandes/pcp,adfernandes/pcp,adfernandes/pcp,adfernandes/pcp