feat: add support for gateway API in the helm chart - #42

Adds optional Gateway API HTTPRoute support to the Helm chart as an alternative to Ingress.

Changes:

• Adds configurable HTTPRoute values.
• Renders an optional route to the bbook Service.
• Updates generated chart documentation.

Suppressed comments (3)

charts/bbook/README.md:55

• This generated README entry now drops the rendered through tpl behavior even though values.yaml still documents it and templates/extra-objects.yaml calls tpl for every object. That makes an important chart capability, such as templated ExternalSecrets, invisible to users; keep the description synchronized with the source comment.

| extraObjects | list | `[]` | extra Kubernetes objects deployed with the chart, rendered through tpl. |

charts/bbook/README.md:82

• The README no longer warns that each replica runs its own Zoho sync job and search index, but values.yaml still documents this behavior. Omitting it can lead operators to scale the deployment and unintentionally duplicate Zoho synchronization work; retain the warning in the generated documentation.

| replicaCount | int | `1` | number of replicas to launch. Note: every replica runs its own Zoho sync job and search index |

charts/bbook/values.yaml:84

• parentRefs is rendered directly as an array, but this example is written as a single mapping. Copying it produces parentRefs: {name: ..., namespace: ...} and the API server rejects the HTTPRoute schema; show list syntax such as [{name: infra, namespace: infra-kgateway}] and regenerate the README description.

  # -- gateways to attach to, e.g. {name: infra, namespace: infra-kgateway}

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Lite