Support host and port mapping for cluster connections (not only SSL)

Expected behavior

When connecting to a cluster which is run inside Docker (e.g. using http://testcontainers.org library, which maps ports dynamically depending on available ones) JedisCluster should take a mapping function to properly map discovered nodes host/port to their real ports.

Actual behavior

Jedis connects to the node(s) using host/port specified in JedisCluster constructor, then discovers all nodes and fails when trying to connect to them directly.

Proposed solution

Use JedisClusterHostAndPortMap not only for SSL connections. Is it a way to go?