Initializing Consul connection log line missing CTS Enterprise

[mkam]

Describe the bug

Previously in CTS Enterprise, there was an INFO log line indicating that CTS was attempting to connect to Consul when it was doing connecting for the first time. This line is no longer outputted, so if the connection to Consul is hanging, there's no context to why CTS hanging until the connection times out. This is the case even if the logs are in TRACE.

It will eventually error and log the reason, but this is a UX regression since CTS used to let the user know that it was in the process of testing the Consul connection.

This is not an issue with the OSS version of CTS.

Before:

$ consul-terraform-sync --config-file=config.hcl
2022-06-09T16:52:32.536-0500 [INFO]  cli: v0.5.2+ent (eab8e1e)
2022-06-09T16:52:32.537-0500 [INFO]  cli: running controller in daemon mode
2022-06-09T16:52:32.537-0500 [INFO]  cli: setting up controller: type=readwrite
2022-06-09T16:52:32.538-0500 [INFO]  ctrl: initializing Consul client and testing connection

After:

$ consul-terraform-sync start --config-file=config.hcl
2022-06-09T16:53:35.517-0500 [INFO]  cli: v0.6.0+ent (a8ecbe4)

Versions

Consul-Terraform-Sync
v0.6.0

Expected Behavior

An INFO level log message indicating that CTS has started to attempt to connect to Consul. Does not necessarily have to be the exact same log message as before, but needs to at least convey the same information.

Actual Behavior

No log message on any level.

Steps to Reproduce

1. Configure the Consul agent address config to hashicorp.com:8500
2. Start CTS