Redis Client: deprecate hash-slot-cache-ttl and add topology-cache-ttl

This commit shall not be backported, because it deprecates a config option
for removal since Quarkus 3.30.

Author: Ladicek

extensions/redis-client/runtime/src/main/java/io/quarkus/redis/runtime/client/VertxRedisClientFactory.java

@@ -102,7 +102,7 @@ public void accept(Set<URI> uris) {
         config.poolRecycleTimeout().ifPresent(d -> options.setPoolRecycleTimeout((int) d.toMillis()));
         // the Vert.x Redis client will only unify `topologyCacheTTL` and `hashSlotCacheTTL` in version 5.1,
         // but in Quarkus, we unify them already
-        long topologyCacheTtl = config.hashSlotCacheTtl().toMillis();
+        long topologyCacheTtl = config.topologyCacheTtl().orElse(config.hashSlotCacheTtl()).toMillis();
         options.setHashSlotCacheTTL(topologyCacheTtl);
         options.setTopologyCacheTTL(topologyCacheTtl);
 

extensions/redis-client/runtime/src/main/java/io/quarkus/redis/runtime/client/config/RedisClientConfig.java

@@ -147,6 +147,13 @@ public interface RedisClientConfig {
     @ConfigDocDefault("resp3")
     Optional<ProtocolVersion> preferredProtocolVersion();
 
+    /**
+     * @deprecated use {@code quarkus.redis.topology-cache-ttl}
+     */
+    @Deprecated(forRemoval = true, since = "3.30")
+    @WithDefault("1s")
+    Duration hashSlotCacheTtl();
+
     /**
      * The TTL of the topology cache. A topology cache is used by a clustered Redis client
      * and a sentinel Redis client to prevent constantly sending topology discovery commands
@@ -156,7 +163,7 @@ public interface RedisClientConfig {
      * Redis client and has no effect otherwise.
      */
     @WithDefault("1s")
-    Duration hashSlotCacheTtl();
+    Optional<Duration> topologyCacheTtl();
 
     /**
      * Whether automatic failover is enabled. This only makes sense for sentinel clients