Description of the problem: When the MTA workflow successfully generates a report, the generated URL that links to the report in the orchestrator UI is to an internal service route which is not available outside the cluster:  

{1 item"workflowdata":{1 item"result":string"report will be ready here -> http://mta-ui.openshift-mta.svc.cluster.local/hub/applications/1/bucket/windup/report"}}

However, in the mta UI the report is available at the MTA UI's external route:

https://mta-openshift-mta.apps.ocp-edge-cluster-0.qe.lab.redhat.com/hub/applications/1/bucket/windup/report/

The local service was configured as the MTA endpoint in the initial configurations for the MTA workflow:

mta.endpoint = mta-ui.openshift-mta.svc.cluster.local

However, the generated report link in the orchestrator UI should also use the externally accessible route.

How reproducible:
100%

Steps to reproduce:

1. Deploy the MTA Workflow on a OCP cluster that has the orchestrator installed via Helm chart 0.1.5

2. Run the MTA workflow successfully on a repo of your choice

3. The workflow should generate link the completed report.

Actual results: Links to internal service route which not externally accessible.

Expected results: Link to report should be to the external MTA UI route, matching the link to the report in the MTA UI, and be accessible.