`unit/cluster/availability-zone.tcl` was the last suite still red from the
merge, and for the same reason as the other three: the test file arrived,
the source did not. Recovered both halves of the feature:
4e7ebb0e9 availability-zone field in CLUSTER SHARDS / SLOTS (#3156)
80790267b the same field in the reply schemas (#3352)
The config existed (`config.c` already created `availability-zone`), which
is what made this one read like a test bug rather than a missing feature —
setting it worked, nothing ever reported it.
Tests: unit/cluster/availability-zone 3/3, was 0/3.
Full suite after all four recoveries: **4,365 ok**, and the only remaining
failures do not reproduce alone —
`cluster-migrateslots/Simultaneous imports` asserts on a *total sync count*
and is sensitive to concurrent load (97/97 on its own), and the
`bg_block_op` exception is a tmp-dir cleanup race. Both are artifacts of
`--clients 4`, not defects.
Co-authored-by: Hanzo Dev <[email protected]>