Description of problem:
When the user imports a git repository and builds it with s2i it automatically creates a service and expose 8080 independent from the user "Route" "Target port" configuration.

Version-Release number of selected component (if applicable):
4.6+

How reproducible:
Always

Steps to Reproduce:
1. Switch to developer perspective and create a fresh namespace if needed
2. Navigate to Add > Git repository > Import from Git
3. Enter Git URL which uses another port then 8080, for example https://github.com/nodeshift-blog-examples/react-web-app
4. Ensure that the s2i flow is selected
5. Click "Show advanced Routing options"

Scenario 1:
6. "Target port" shows the placeholder 8080
7. "Create" the Deployment without additional changes

Scenario 2:
6. Click into the "Target port" field, enter "3000" and press "Create 3000"
7. "Create" the Deployment without additional changes

Actual results:
Scenario 1: A Service is created which expose port 8080; and a Route which exports port 8080. (Doesn't work for the given git repo.)
Scenario 2: A Service is created which expose port 8080 and port 3000; and a Route which exports 3000. (This is fine for the given git repo.)

Expected results:
Scenario 1: okay, exposing the port 8080 is fine
Scenario 1: exposing just port 3000 in the service

Additional info:
oc new-app doesn't support an option to change the service port, it always creates a service which expose port 8080.