fix(redis): load Redis connection beans when Redis is used for queues

[bulgarian-beast]

Fixes #991

Summary

This fixes a startup regression where Conductor fails to boot when Redis is configured only as the queue backend, such as in the MySQL + Redis Docker Compose setup.

Root cause

Redis connection configuration classes were only activated when conductor.db.type matched a Redis mode, but queue autoconfiguration also requires these beans when conductor.queue.type is set to Redis.

Changes

• make standalone Redis connection config load for queue usage as well
• make cluster Redis connection config load for queue usage as well
• make sentinel Redis connection config load for queue usage as well
• add a sentinel condition class
• add a regression test covering queue-only Redis activation

Validation

• ./gradlew spotlessApply
• ./gradlew :conductor-redis-configuration:test --tests com.netflix.conductor.redis.config.RedisConnectionConditionTest
• docker compose -f docker/docker-compose-mysql.yaml up --build -d
• verified http://localhost:8000/health returns healthy

[mp-orkes]

@bulgarian-beast thank you! LGTM. Please rebase on top of main to fix the conflict with RedisSentinelConfiguration.java (caused by #951 landing after your branch point). Once done I'll approve and merge.

[bulgarian-beast]

Hi @mp-orkes

Rebased on top of main and resolved the RedisSentinelConfiguration.java conflict in 17743b5.

Re-validated with:

• ./gradlew spotlessApply
• ./gradlew :conductor-redis-configuration:test --tests com.netflix.conductor.redis.config.RedisConnectionConditionTest
• docker compose -f docker/docker-compose-mysql.yaml up --build -d
• verified http://localhost:8000/health returns healthy

Could you please re-review and approve when you have a moment?

[mp-orkes]

LGTM