consider Consul TLS config in envoy bootstrap hook

[shoenig]

Currently the envoy bootstrap task runner hook directly uses the value from the agent's consul.address parameter for passing into the invocation of consul connect envoy -boostrap -http-addr flag. This value is used by the invoked Consul CLI to communicate with the specified Consul agent for generating the envoy bootstrap config. We are not respecting the TLS/auth config options, which I think we can pass through using environment variables when doing the exec consul

• auth -> CONSUL_HTTP_AUTH https://www.consul.io/docs/commands/index.html#consul_http_auth
• ca_file -> CONSUL_CACERT https://www.consul.io/docs/commands/index.html#consul_cacert
• cert_file -> CONSUL_CLIENT_CERT https://www.consul.io/docs/commands/index.html#consul_client_cert
• key_file -> CONSUL_CLIENT_KEY https://www.consul.io/docs/commands/index.html#consul_client_key
• ssl -> CONSUL_HTTP_SSL https://www.consul.io/docs/commands/index.html#consul_http_ssl

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.