CLI should be able to run with or without TLS

[jakedoublev]

Background

The CLI is currently hardcoded to run without a secure TLS connection and to dial http://localhost:<port>. The platform TLS story is maturing¹ and once it is stabilized within the SDK, the CLI should support the ability to drive with or without TLS so it can successfully dial the platform port in either scenario.

Acceptance Criteria

1. CLI does not hardcode http platform endpoints
2. CLI's SDK initializations include the sdk.WithInsecureConnection() option only when running without TLS enabled
3. config is updated to include a TLS enabled true/false flag
4. the config subcommand is updated to drive the TLS enabled state and update the config when ran
5. the error message with code Unavailable and desc "connection error" is transformed into a more helpful error message to the user like "Failed to dial the platform, please check that it is running on ".

Footnotes

1. https://github.com/opentdf/platform/issues/451 ↩

[jrschumacher]

This was completed with #152