Add ability to specify client certificate and associated private key via base64 values in config

[mastermanu]

Adds support for passing in client certificate / password data via the configuration through the use of "CertData" and "KeyData" fields respectively.

One can simply do:

cat <certificate or key> | base64 --wrap=0

and then paste the output as a value for each of the fields.

For now, both the client certificate and the key must be passed in via the same style (e.g. passing the certificate via a filepath and its associated key via base64 is not supported). This is not difficult to add, but will only add this if requested.

Verification:

• Canary and Bench Tests pass against both local and deployed environments that point a Cluster with TLS enabled.