[Enhancement] Possibility for a Lettuce variant of "ebean-redis"?

Personally I find Lettuce to be the modern client. Jedis brings in dependencies such as gson, org.json:json, but is also just not a very well made client, whereas both Lettuce and Redisson are arguably much better quality clients.

Proposed naming scheme could be any of the following:

• Renaming ebean-redis:
  • ebean-jedis
  • ebean-lettuce
  • ebean-redisson
• Suffix instead:
  • ebean-redis - aggregator/bundle
  • ebean-redis-jedis
  • ebean-redis-lettuce
  • ebean-redis-redisson

In any case, it should be trivial to at least support Lettuce so we have one high-quality implementation to target. I'm unsure what the correct abstraction for a connection would be to support both regular, cluster, etc connections, but I'm thinking instead of providing/injecting our own client connection (and having to deal with the complexity of this), there can instead be connection configuration and ebean connect to the server automatically, using cluster if needed depending on config etc.

Review the existing ebean-redis/Jedis integration and its connection configuration first, then compare how regular and cluster connections are represented. Done requires a decided module naming and connection approach that supports Lettuce alongside the existing behavior, with coverage for the supported connection modes.