pmlogger scripts: really use default pmcd timeouts by default

pmlogger scripts: really use default pmcd timeouts by default

Somehow, at some point in the distant past, the "far-away" pmcd
timeouts became enabled by default in the pmlogger control file.
Make these match the pmie control file, which uses the correct
defaults and has a helpful comment about non-default values.

Add a one-trip guard to pmlogconf so that it will fail-fast in
the mode where a remote pmcd takes ages to respond (otherwise,
it will iteratively call pmprobe, and each separate invocation
is subject to the pmcd connection timeout).

While investigating, found pmcd_wait could mis-report timeouts
in its verbose/diagnostic mode, so cleaned that up here too.