Add a configuration option to the Redis client in debezium-storage-redis to optionally specify keystore and truststore similar to how connectors like binlong and mongodb allow for custom keystore and truststore.

This would allow the Redis sink to use different keystore/truststore than the ones supplied by Java's system properties and used by other clients.

Having different keystore/truststore allows for an isolated security context when connecting to a Redis server and facilitate easier deployment in cloud architecture.

The implementation will:

1. Add configuration options for keystore and truststore (including path to the file, optional password and optional type of the store) in debezium-storage-redis
2. Update the Jedis client to version 6.0.0 which allows setting custom SSL options for the client.
3. Update the Redis stream consumer in debezium-server to reflect the configuration changes
4. Add integration tests to debezium-server