fix e2e tests: gateway tls listeners must specify tls (#10659)

Author: puertomontt

changelog/v1.19.0-beta13/tls-tests.yaml

@@ -0,0 +1,4 @@
+changelog:
+  - type: NON_USER_FACING
+    description: >-
+      "fix e2e tls route tests that were failing on nightlies using GW API v1.0.0"

test/kubernetes/e2e/features/services/tlsroute/testdata/cross-ns-gateway-and-client.yaml

@@ -9,6 +9,8 @@ spec:
       port: 8443
       protocol: TLS
       hostname: "example.com"
+      tls:
+        mode: Passthrough
 ---
 apiVersion: v1
 kind: Pod

test/kubernetes/e2e/features/services/tlsroute/testdata/cross-ns-no-refgrant-gateway-and-client.yaml

@@ -9,6 +9,8 @@ spec:
       port: 8443
       protocol: TLS
       hostname: "example.com"
+      tls:
+        mode: Passthrough
 ---
 apiVersion: v1
 kind: Pod

test/kubernetes/e2e/features/services/tlsroute/testdata/multi-listener-gateway-and-client.yaml

@@ -5,7 +5,7 @@ metadata:
 spec:
   gatewayClassName: gloo-gateway
   listeners:
-  - name: listener-6443 # do one listener with multiple hostnames? 
+  - name: listener-6443  
     protocol: TLS
     port: 6443
     hostname: "example.com"
@@ -17,6 +17,9 @@ spec:
   - name: listener-8443
     protocol: TLS
     port: 8443
+    hostname: "example.com"
+    tls:
+      mode: Passthrough
     allowedRoutes:
       kinds:
       - kind: TLSRoute