TLS_VERIFY setting behaves differently for docker and docker-autoscaler executors

Customer report, needs verifying:

When using a socket and specifying tls_verify on the docker executor, it ignores the tls_verify setting. However when using docker-autoscaler it respects it. So when tls_verify=true and using the docket on docker executor, the TLS setting doesn't matter. But when moving to docker-autoscaler it does, and so it can break. This required one customer to set tls_verify=false to make it work (even though it didn't matter), which raised some red flags. It should work consistently between these two executors.