To use port number instead of port name

[cniackz]

fixes: #1984

Objectives:

• To fix HTTPS not working for operator console when deployed with Helm chart #1984
• To ensure flexibility in selecting the port number for the Operator console, whether utilizing TLS or not.

Current problem:

• We are hardcoding service.port.name to be http only, necessitating patching.

  rules:
    - host: {{ .Values.console.ingress.host }}
      http:
        paths:
          - path: {{ .Values.console.ingress.path }}
            pathType: {{ .Values.console.ingress.pathType }}
            backend:
              service:
                name: "console"
                port:
                  name: http <------- here

Solution:

• By utilizing service.port.number, we provide flexibility in port selection, enabling users to choose TLS on or off according to their requirements, without requiring them to patch our ingress.

Documentation:

• The documentation regarding port types can be found at: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-rules.

A list of paths (for example, /testpath), each of which has an associated backend defined with a service.name and a service.port.name or service.port.number. Both the host and path must match the content of an incoming request before the load balancer directs traffic to the referenced Service.

Notice is either one or the other but not both: service.port.name or service.port.number

[ravindk89]

One clarifying comment

[cniackz]

Sorry I don't want to merge until all tests are passing

[cniackz]

Tests will be fixed in: #2062