Use TLSRoute v1 in anticipation of gateway-api bump to 1.5.1

[peterbangert]

Description

With the pending bump from gateway-api 1.4.1 to 1.5.1

• ref: feat(deps): bump sigs.k8s.io/gateway-api from 1.4.1 to 1.5.1 #1104

As well with envoy gateway preparing to bump to gateway-api 1.5.1

• ref: https://github.com/envoyproxy/gateway/blob/c5f54a209db6faf8dbec1cf803778b16b168f93a/charts/gateway-crds-helm/templates/experimental-gatewayapi-crds.yaml#L28

It would be prudent to prepare a PR to anticipate these changes as gateway-api 1.5 has introduced validating admission policy (VAP) which prevents downgrading to a version prior to 1.5 after you've installed Gateway API 1.5.

• https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.5.0

Effectively more changes will be required than dependabots proposals to ensure functionality when interacting with latest envoy gateway and bumping gateway-api versions.