NFR zero downtime scale test errors when sending https traffic

[bjee19]

In the most recent bi-weekly run of our nfr tests #3079, there are errors in both oss and plus test runs when sending traffic to our https endpoint.

https://github.com/nginx/nginx-gateway-fabric/blob/a6a8cef71d9dfe55d26ab0e594fa695f56bdabde/tests/results/zero-downtime-scale/edge/edge-oss.md

https://github.com/nginx/nginx-gateway-fabric/blob/a6a8cef71d9dfe55d26ab0e594fa695f56bdabde/tests/results/zero-downtime-scale/edge/edge-plus.md

You can see that all our traffic to the /tea endpoint results in all 0's coming back.

This is the given error: Get "https://cafe.example.com/tea": remote error: tls: unrecognized name

[bjee19]

Issue will be resolved in #3137.

Quick fix would be to change the zero-downtime cafe-routes.yaml tea HTTPRoute from:

---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tea
spec:
  parentRefs:
  - name: gateway
    sectionName: https
  hostnames:
  - "cafe.example.com"
  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /tea
    backendRefs:
    - name: tea
      port: 80

to

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tea
spec:
  parentRefs:
  - name: gateway
    sectionName: https
  hostnames:
  - "*.example.com"
  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /tea
    backendRefs:
    - name: tea
      port: 80