Initial implementation of Client Cert mechanism
Minor refactoring of Client Cert implementation following post HttpCompletionHandler removal changes.
Adjustment so that the SSLSession is the current session and not a cached session, this is for a couple of reasons: -
 1 - Firstly the session is not established until the channel is actually used, any cached session is for a pre-handshake state.
 2 - Renegotiation is theoretically possible which again means a cached session may no longer be valid.
Completion of the test to verify that ClientCert authentication occurred.
Minor addition to enable CLIENT-CERT for deployed web apps.