This issue is a follow-up to KOGITO-5284. 

Today the Kogito Kubernetes Add-On has incorporated an `AbstractDiscoveredEndpointCaller` class to wrap the discovery capability into WIHs. Unfortunately, this is far from the ideal since the WIH is interested in using this add-on and not the other way around.

Additionally, this class is making HTTP requests, which shouldn't be doing since we already have the REST and the OpenAPI WIH for this work.

This issue should solve this problem by optionally incorporating the Kubernetes services discoverability in the REST and OpenAPI WIH. So, instead of a user adding the endpoint information manually in the configuration, the engine would discover it automatically when deployed on Kubernetes.