feat(httproute): add optional timeouts field

[Petersmit27]

Description of the change

When using Gateway API's HTTPRoute, adds the option to configure the timeouts block (Gateway API docs)

I found that the setup check on Nextcloud's /settings/admin/overview page times out because the request takes ~35 seconds. I run Envoy, which handles a 15 second timeout by default.

Benefits

Allows for more customisation using standard features in the Gateway API spec. (nothing implementation-specific)

Possible drawbacks

Internal structure of the timeouts block not declared and must be formed correctly in the values by the user. I figured this would be okay, since the matches and filters blocks behave the same way and are more complex. Please let me know if this should be changed, however.

Parameters are also not documented in the README, but so is the rest of the HTTPRoute setup...

Applicable issues

• N/A (didn't make one)

Additional information

• Tested locally with the following values:

httpRoute:
  enabled: true
  hostnames:
    - my.example.hostname
  parentRefs:
    - name: main
      namespace: envoy-gateway-system
      sectionName: https-gateway
  rules:
    - timeouts:
        request: "300s"

And helm template nextcloud charts/nextcloud --values examplevalues.yaml --show-only templates/route.yaml to generate the route. Applied this to my cluster and the request doesn't time out now.

Bumped the chart a minor version because semver says I should bump "MINOR version when you add functionality in a backward compatible manner". Please let me know if that's OK in this case :)

Checklist

• I have read the CONTRIBUTING.md doc.
• DCO has been signed off on the commit.
• Chart version bumped in Chart.yaml according to semver.
• (optional) Parameters are documented in the README.md