feat: CDI-managed Lettuce beans with Vert.x event loop integration

[vchomakov]

CDI-managed Lettuce beans with Vert.x event loop integration

Builds on top of the Lettuce + Vert.x foundation from the previous PR to provide seamless CDI injection of Lettuce Redis beans.

What this PR adds

Deployment processor (LettuceProcessor) with two build steps:

• detectLettuceUsage — scans injection points for Lettuce types (RedisClient, StatefulRedisConnection, ClientResources) and emits build items only for clients that are actually needed
• init — registers synthetic CDI beans per client name via the recorder

Runtime recorder (LettuceRecorder) that manages the full lifecycle:

• Creates shared ClientResources backed by Vert.x event loops
• Creates per-client RedisClient and StatefulRedisConnection instances
• Handles shutdown in correct order: connections → clients → resources
• Supports checkActive guards for clear error messages on misconfigured clients

Lettuce-specific build item (RequestedLettuceClientBuildItem) to isolate Lettuce bean creation from other Redis processors (Vert.x Redis, Redis Cache, OIDC Redis). This prevents Lettuce from attempting connections for non-Lettuce clients.

Usage

// Default client
@Inject
StatefulRedisConnection<String, String> connection;

// Named client
@Inject
@RedisClientName("my-redis")
StatefulRedisConnection<String, String> connection;

Tests

• Default client injection + SET/GET operations
• Named client with @RedisClientName
• Multiple clients (default + two named) sharing ClientResources
• Inactive client (active=false) produces clear InactiveBeanException
• Missing hosts produces clear InactiveBeanException