Gateway render logic precludes possibility of using TLS for a protocol

Bug

Description

Describe the problem, what were you doing when you noticed the bug?

Chart was not rendering correctly after upgrade. TLS protocol is now not being recognized after previous fix here

Provide any steps possible used to reproduce the error (ideally in an isolated fashion).

Define a gateway like the one below in values:

           
         gateways:
           app-tcp:
             ingressGateway: "mtls-ingressgateway"
             autoHttpRedirect:
               enabled: false
             hosts:
               - "app-tcp.staging.dso.mil"
             servers:
             - hosts:
               - "app-tcp.staging.dso.mil"
               port:
                 name: tcp-mtls
                 number: 8443
                 protocol: TLS
               tls:
                 mode: MUTUAL

BigBang Version

What version of BigBang were you running?

2.37.0

This can be retrieved multiple ways:

# via helm
helm ls -n bigbang

# via the deployed umbrella git tag
kubectl get gitrepository -n bigbang

Proposed solution is to use the if logic to detect either HTTPS or TLS because TLS is the only option for a TCP backend. Otherwise, applying HTTP to TCP traffic renders the backend and the gateway unusable