PoolingHttpClientConnectionManager unsafe volatile field access

PoolingHttpClientConnectionManager assumes subsequent volatile reads on validateAfterInactivity and defaultSocketConfig result in the same value, which can result n incorrect assumptions or even null pointer exceptions.

We should read a snapshot to a local variable, and reuse the local snapshot.