New Redis Client API

[cescoffier]

The current Redis extension does not provide all the possibilities Redis offers, and the API is not easy to use.

This PR provides a new high-level and type-safe Redis API that covers the previous API's shortcomings.

The previous API is still available but deprecated.

Breaking Changes

Unfortunately, while refactoring the extension, I had to break a few things:

• Host Providers are now identified using @Identifier instead of @Named (following @mkouba's advice)
• It is not possible to create dynamic clients - this was done to support pub/sub, which is now supported by the API

What's missing (and will come later)

The PR is already big enough, and some parts will be provided later without breakage:

• the commands from the stream group are not yet provided (you can use custom commands for the time being)
• scan operations should provide a flattened stream (so instead of retrieving batches, retrieves the element individually)
• metrics have been left off for now. It's possible to implement a micrometer binder (work in progress)
• the LCS command does not provide the IDX option

Related issues

• Fix ReactiveRedisClient: Transaction with multi() not working #24056
• Fix How to use Redis pub/sub with Quarkus and ReactiveRedisClient? #21108

[machi1990]

Thanks @cescoffier for this. Very nice improvements.

I'll have a proper look in the next couple of days.

[ebullient]

Is it too much to ask to bring the appropriate doc templates into your new docs?
#25354

docs/src/main/asciidoc/redis.adoc -- Is that meant to be a tutorial? (I believe so.. )
docs/src/main/asciidoc/redis-reference.adoc -- this feels like a combination of a how-to (installation), and a reference (how the extension works and config options, etc.) .. can we split them so we get the docs roughly better in the first pass? (I am happy to help in that regard.. )

[machi1990]

I left some minor doc suggestions, otherwise lgtm.

Will it be possible to add a migration note as well as there are some breaking changes?

I love the direction that this is taking with typesafety, repository style api, thanks @cescoffier for the PR.

[quarkus-bot]

Failing Jobs - Building 31af6c9

Status	Name	Step	Failures	Logs	Raw logs
✖	Maven Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Maven Tests - JDK 11 Windows #

- Failing: integration-tests/maven 

📦 integration-tests/maven

✖ io.quarkus.maven.it.DevMojoIT.testCapabilitiesConflict line 108 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

✖ io.quarkus.maven.it.DevMojoIT.testCapabilitiesConflict line 108 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)