v0.2.6

feat(crd): add default timeout field to MCPServerSpec (#121)

### Summary

Adds a `Timeout` field to `MCPServerSpec` with a kubebuilder default of
`30s`.

This addresses
[kagent-dev/kagent#1272](https://github.com/kagent-dev/kagent/issues/1272):
MCP servers deployed via the MCPServer CRD use a sidecar gateway that
spawns a new stdio process (e.g. via `uvx`/`npx`) for each session.
Process startup can take 2–8 seconds depending on package cache state,
which exceeds the default 5-second timeout used by some ADK clients
(e.g. Python ADK `StreamableHTTPConnectionParams`), causing intermittent
`"Failed to create MCP session"` errors.

### Context

An initial fix was proposed in
[kagent-dev/kagent#1275](https://github.com/kagent-dev/kagent/pull/1275)
by making the timeout configurable via the Helm chart (env var →
controller flag → handler threading). A maintainer [correctly pointed
out](https://github.com/kagent-dev/kagent/pull/1275#issuecomment-) that
the proper fix is to add this field to the MCPServer CRD itself, which:

- Follows existing CRD patterns (`Port` has `+kubebuilder:default=3000`,
`Replicas` has `+kubebuilder:default=1`)
- Provides **per-resource granularity** (each MCPServer can specify its
own timeout)
- Eliminates complex threading through Helm/env/flags/handlers
- Is the Kubernetes-idiomatic approach

### Changes

| File | Description |
|------|-------------|
| `api/v1alpha1/mcpserver_types.go` | Add `Timeout *metav1.Duration`
field with `+kubebuilder:default="30s"` |
| `api/v1alpha1/zz_generated.deepcopy.go` | Regenerated via `make
generate` |
| `config/crd/bases/kagent.dev_mcpservers.yaml` | CRD manifest
regenerated via `make manifests` |
| `helm/kmcp-crds/templates/mcpserver-crd.yaml` | Helm CRD template
updated to match |

### Backward Compatibility

- The default value is `30s` — existing MCPServer resources without an
explicit timeout will automatically get this default applied by the API
server.
- No breaking changes to existing CRs.

### Companion PR

Once this is merged and released, I will create a new PR and the kagent
controller will be updated to propagate this field:
`ConvertMCPServerToRemoteMCPServer` propagates `MCPServer.Spec.Timeout`
→ `RemoteMCPServer.Spec.Timeout`

Ref:
[kagent-dev/kagent#1272](https://github.com/kagent-dev/kagent/issues/1272)

Signed-off-by: skhedim <sebastien.khedim@gmail.com>