Use services instead routes to inner communication between Kogito services

Today, the Kogito Operator creates a Route for the any service (support or custom) deployed on OpenShift.

Exposing the service by default could lead to problems such as:

1. Users that don't realize that the service is exposed and should not
2. Internal services that don't need/should be exposed
3. Opens a breach where users can ask for features that is a Route scope, like enabling TLS

This proposal is to NOT expose the service by default, but instead create a simple Route/Ingress like we are doing today if an option like "expose" is on.

The Route/Ingress should not be reconciled. Instead, after creating it the operator should not touch in any further modifications made by the users.

This feature should be advised to be used only on "development" scenarios. On production environments the service exposition should be done by administrators instead.

Since we use external URL all the time to create communication between services, this should be tracked. Ideally, the URL injection should be:

1. Use the external route created by the user
2. Use service URL whenever possible