Add new --run-port flag to odo init to set ports non-interactively

[rm3l]

What type of PR is this:
/kind feature
/area init

What does this PR do / why we need it:
This introduces a new --run-port repeatable flag to odo init, allowing to set application ports non-interactively. It looks into the fetched Devfile for any default (or single non-default) run command; and, if it is an exec command, tries to find the referenced container component to overwrite its endpoints.

More context in #6925

Which issue(s) this PR fixes:
Fixes #6925

PR acceptance criteria:

• Unit test

• Integration test

• Documentation

  • https://odo-dev-pr-6953.odo-test-kubernete-449701-49529fc6e6a4a9fe7ebba9a3db5b55c4-0000.eu-de.containers.appdomain.cloud/docs/command-reference/init#non-interactive-mode
  • Specify the application ports

How to test changes / Special notes to the reviewer:

• No error if the Devfile does not have a run command;

$ odo init --name udi --devfile udi --run-port 8080 --run-port 9090
  __
 /  \__     Initializing a new component
 \__/  \    
 /  \__/    odo version: v3.12.0
 \__/

 ✓  Downloading devfile "udi" [16ms]

Your new component 'udi' is ready in the current directory.
To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
Changes will be directly reflected on the cluster.

$ yq '.components[] | select(has("container")) | del(.container.env) | del(.container.volumeMounts) | split_doc' devfile.yaml
container:
  cpuLimit: 4000m
  cpuRequest: 1000m
  image: quay.io/devfile/universal-developer-image:ubi8-latest
  memoryLimit: 6G
  memoryRequest: 512Mi
  mountSources: true
name: tools

• It should overwrite the container endpoints with the ones coming from --run-port

$ odo init --name my-nodejs --devfile nodejs --run-port 18080 --run-port 28080 --run-port 38080
  __
 /  \__     Initializing a new component
 \__/  \    
 /  \__/    odo version: v3.12.0
 \__/

 ✓  Downloading devfile "nodejs" [18ms]

Your new component 'my-nodejs' is ready in the current directory.
To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
Changes will be directly reflected on the cluster.

$ yq '.components[] | select(has("container")) | del(.container.env) | del(.container.volumeMounts) | split_doc' devfile.yaml
container:
  args:
    - tail
    - -f
    - /dev/null
  endpoints:
    - name: port-18080-tcp
      protocol: tcp
      targetPort: 18080
    - name: port-28080-tcp
      protocol: tcp
      targetPort: 28080
    - name: port-38080-tcp
      protocol: tcp
      targetPort: 38080
  image: registry.access.redhat.com/ubi8/nodejs-16:latest
  memoryLimit: 1024Mi
  mountSources: true
name: runtime

• It should overwrite the container endpoints with the ones coming from --run-port, even if the Devfile stack in the registry has many container components; example with java-wildfly:

$ odo init --name my-java-wildfly --devfile java-wildfly --run-port 1234 --run-port 5678 --run-port 9012
  __
 /  \__     Initializing a new component
 \__/  \    
 /  \__/    odo version: v3.12.0
 \__/

 ✓  Downloading devfile "java-wildfly" [44ms]

Your new component 'my-java-wildfly' is ready in the current directory.
To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
Changes will be directly reflected on the cluster.

$ yq '.components[] | select(has("container")) | del(.container.env) | del(.container.volumeMounts) | split_doc' devfile.yaml
container:
  endpoints:
    - name: port-1234-tcp
      protocol: tcp
      targetPort: 1234
    - name: port-5678-tcp
      protocol: tcp
      targetPort: 5678
    - name: port-9012-tcp
      protocol: tcp
      targetPort: 9012
  image: quay.io/wildfly/wildfly-centos7:26.1
  memoryLimit: 1512Mi
  mountSources: true
name: wildfly
---
container:
  endpoints:
    - name: tracing-ui-wild
      targetPort: 16686
  image: quay.io/jaegertracing/all-in-one:1.27
  memoryLimit: 128Mi
name: jaeger

[netlify]

🔨 Deploy Preview deleted from internal cluster!

Name	Link
🔨 Latest commit	76f96e2
😎 Deploy Preview	https://odo-dev-pr-6953.odo-test-kubernete-449701-49529fc6e6a4a9fe7ebba9a3db5b55c4-0000.eu-de.containers.appdomain.cloud/

[odo-robot]

Windows Tests (OCP) on commit 996ab8e finished successfully.
View logs: TXT HTML

[odo-robot]

OpenShift Unauthenticated Tests on commit 996ab8e finished successfully.
View logs: TXT HTML

[odo-robot]

NoCluster Tests on commit 996ab8e finished successfully.
View logs: TXT HTML

[odo-robot]

Unit Tests on commit 996ab8e finished successfully.
View logs: TXT HTML

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[odo-robot]

Validate Tests on commit 996ab8e finished successfully.
View logs: TXT HTML

[odo-robot]

Kubernetes Tests on commit 996ab8e finished successfully.
View logs: TXT HTML

[odo-robot]

OpenShift Tests on commit 996ab8e finished successfully.
View logs: TXT HTML

[odo-robot]

Kubernetes Docs Tests on commit 5911930 finished successfully.
View logs: TXT HTML