Allow TLS transport/authentication when connecting to engines

Currently interlock cannot speak to the engine APIs if the engines (Docker) are running with `tlsverify` (ensure that clients present certificates signed by `tlscacert`).

Also, probably even if `tlsverify` is not used, interlock will probably fail to connect due to x509 validation.

This PR adds options that mirror those that the Docker daemon provides.