Is your feature request related to a problem? Please describe.
When using ReactiveResilience4JCircuitBreakerFactory, Spring Cloud Circuit Breaker silently applies a default TimeLimiterConfig with a 1-second timeout — even when the user never configured one.

Resilience4j itself treats CircuitBreaker and TimeLimiter as completely separate, independent modules. Users coming from plain Resilience4j would never expect a TimeLimiter to be created in automatically.

Describe the solution you'd like
I totally understand the original intent — in reactive streams, a hanging request never completes, so the circuit breaker never records a failure. TimeLimiter was added to solve that.

But I think the right approach, Something like:

• Throw a clear error or warning if no TimeLimiterConfig is provided
• Or at minimum, log a prominent warning like:

  No TimeLimiterConfig found for circuit breaker 'my-cb'. Defaulting to 1 second. Please configure this explicitly for production use.