make rustls as default TLS

[sehz]

With latest release, rustls support IP address certs which in the past, prevent being used in the Kubernetes env.

[ozgrakkurt]

related to #3091

[ozgrakkurt]

@sehz Do we want to keep optional openssl or should it be rustls only?

Also it is not possible to get rid of openssl from repo because we depend on cargo-generate which doesn't seem to be able to work without openssl.

[sehz]

We should keep openssl. Not sure relevance to cargo generate

[smndtrl]

Just wanted to let you know I stumbled upon issues with openssl in our builds as there's no libssl in our new builder and base images. For now that's not a huge problem as we only intend to run our connectors as static binaries in containers starting first release in CY23 Q3

Looking forward to this

[digikata]

Probably good to tackle this a crate at a time

[github-actions]

Stale issue message

[github-actions]

Stale issue message

[digikata]

A new release https://github.com/rustls/rustls/releases/tag/v/0.22.0 (mentioned by Seyho here https://infinyon.slack.com/archives/CQ8UX6SBH/p1701539652032509)

Making rustls the default build config would reduce maintenance for cross platform builds, as well as surface area for security updates in dependencies.

Changes may need to be made in reference to: (though that crate is already configurable for rusttls)
https://github.com/infinyon/future-aio (fluvio-future crate) as well as in this fluvio repo.