feat: add support for connect specific https configs

[vcrfxia]

Description

Fixes #6631.

This PR adds support for TLS configs to configure ksqlDB requests to an external Connect deployment. Configs prefixed with ksql.connect. are applied only to ksqlDB's Connect client. Non-prefixed configs are also applied to ksqlDB's Connect client by default, similar to how ksqlDB handles its Schema Registry TLS configs today.

Example configs:

ksql.connect.url=https://localhost:8443
ksql.connect.ssl.truststore.location=/path/to/client.truststore.jks
ksql.connect.ssl.truststore.password=<some password here>
ksql.connect.ssl.truststore.type=JKS
ksql.connect.ssl.endpoint.identification.algorithm=none

Testing done

I wanted to add an integration test but hit a few dead ends trying to configure an embedded Connect with custom TLS configs. Open to ideas if anyone has any, else I think the change is minor enough that I feel good about the unit tests plus my manual test coverage.

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[jzaralim]

LGTM

[reneveyj]

Thanks for adding this. Now I can finally manage connectors from the ksql CLI :)