Stand up a dev TigerBeetle cluster from this chart

## Summary
Stand up a dev TigerBeetle cluster using this chart. The chart itself is ready; this is an ops action, not chart work.

## Source of truth
`rebuild-roadmap.md`, "The cluster track — runs alongside R3 to R6".

## Current state
`charts/tigerbeetle` publishes to `oci://ghcr.io/adorsys-gis/charts/tigerbeetle`, with `appVersion` pinned to TigerBeetle 0.17.9 (matching the rebuild's design target — `design/tigerbeetle-migration/target-architecture.md` in webank-context). The chart has zero open issues today and its most recent commit (2026-08-07) fixed a real consensus-cluster correctness bug (replica-address ordering by StatefulSet ordinal rather than lexicographic IP sort — verified in `charts/tigerbeetle/templates/common.yaml`'s `zaddresses`/`zwatcher` scripts). Nothing blocks standing up a dev instance today.

## Acceptance criteria
- A dev TigerBeetle cluster is running from this chart (3 replicas, per `values.yaml`'s current hardcoded minimum for TigerBeetle consensus).
- Basic connectivity/health is confirmed (e.g. a client can connect and the cluster reports healthy).

## Dependencies
None — this is the first, cheapest item in the cluster track and can start immediately alongside webank-services R3.

## Out of scope
Any chart changes. If standing up the dev cluster surfaces a chart defect, file it as a separate issue rather than folding fixes into this one.

Start with charts/tigerbeetle/values.yaml and the published OCI chart, then read rebuild-roadmap.md and the referenced target architecture for the required dev setup. Deploy three replicas without changing chart files, verify that a client connects and the cluster reports healthy, and file any chart defect separately.

Scritto dal modello di indicizzazione a partire dal testo della issue.