HF RL Explorer

Issue: ConfigCustomizers for unnamed configurations not applied

Issue: ConfigCustomizers for unnamed configurations not applied: a task in LegoFlow-SWE (Harbor dataset). Description When a custom ConfigCustomizer bean is registered for a specific resilience4j instance name (e.g., my-retry ), but no corresponding configuration entry exists in application.yml…

The task

**Description** When a custom `ConfigCustomizer` bean is registered for a specific resilience4j instance name (e.g., `my-retry`), but no corresponding configuration entry exists in `application.yml` for that instance, the customizer is silently ignored and never applied.

Part of Lego-X/LegoFlow-SWE.