Wiring new methods to old methods

[a-TODO-rov]

Make sure that:

• You have read the contribution guidelines.
• You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
• You applied code formatting rules using the mvn formatter:format target. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.

---

Note

Medium Risk
Touches connection establishment and auto-reconnect address resolution paths (including cluster connect retry logic), so regressions could impact connectivity despite mostly being API wiring/deprecation changes.

Overview
Shifts socket address resolution/connection wiring to prefer Supplier<CompletionStage<SocketAddress>> throughout AbstractRedisClient, ConnectionBuilder, RedisClient, and RedisClusterClient, while marking the prior Mono-based hooks as @Deprecated and adding new *Stage/*Async accessors.

Updates reconnect watchdogs (ConnectionWatchdog, MaintenanceAwareConnectionWatchdog) to wrap async suppliers via Mono internally and exposes wrapSocketAddressSupplierAsync, and rewrites cluster connect retry loops to use CompletableFuture chaining instead of Reactor Mono retry. Unit tests are adjusted to the new Mono-based RebindAwareAddressSupplier API.

^{Reviewed by Cursor Bugbot for commit 2147c44. Bugbot is set up for automated code reviews on this repo. Configure here.}

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2147c44. Configure here.}

[cursor]

Dead private connect methods after refactoring to connectFuture

Low Severity

The two private connect methods returning Mono<T> (one taking StatefulRedisClusterConnectionImpl, the other taking StatefulRedisConnectionImpl) are now unused dead code. All call sites that previously used these methods have been replaced with calls to the new connectFuture methods. A grep confirms no remaining callers exist within this class.

 

^{Reviewed by Cursor Bugbot for commit 2147c44. Configure here.}

[cursor]

Logging uses state.get() instead of captured current variable

Low Severity

Inside wrappedSupplier, the debug log statements at the top of the Mono.defer lambda use state.get() instead of the already-captured current local variable. In a concurrent environment, state could be updated by another thread between the initial read into current and the subsequent state.get() calls, causing the log to show a different state than what the code is actually acting upon. This makes debugging concurrent rebind issues misleading.

 

^{Reviewed by Cursor Bugbot for commit 2147c44. Configure here.}