Context
The component test framework currently hardcodes service names and connection details, causing failures in Clowder-managed environments where services have dynamic names (e.g., "env-ephemeral-5zjamw-featureflags" instead of "unleash").

I was able to use a bandaid solution by creating a manual proxy services and environment-specific workarounds. Then I refactored com.redhat.swatch.component.tests.resources.unleash.OpenShiftUnleashContainerManagedResource a bit to try to dynamically discover service names, which removed the need to make a manual proxy.

But we should implement a more holistic solution for dynamically discovering these values. In our quarkus services, there's a library we can use. Since we're trying to be framework agnostic, there should be some example of how to do this in swatch-tally (because it's still Spring Boot and we implemented a solution from scratch to read from cdappconfig.json)

Acceptance Criteria

• Component test framework reads service endpoints from cdappconfig.json
• No hardcoded service names or connection details
• Tests work in any ephemeral environments without proxy services
• Framework automatically discovers Kafka, database, feature flags, and other services
• Remove existing hardcoded service discovery logic