10.0.0

Remove the temporary cache migration bridge after consumers have completed their v2 rollout.

Breaking API cleanup:

• Remove Utopia\Database\Cache\Bridge and legacy numeric writer bookkeeping. Mutation coordination now always uses the existing opaque-CAS protocol.
• Remove the bridge-only query-epoch TTL argument and obsolete cache-5 compatibility runtime/Docker tier.
• Keep the current v2 data/state format and eviction-safe late-writer behavior. Stable cache 6.1.3 and 7.x are supported.

Query invalidation always purges the caller-owned epoch before rotating it, including a cold local region, so semantic purge replay invalidates a warm remote region. A regression reproduced stale remote data before the fix and fresh recomputation after it.

Upgrade only after all legacy-reading processes and Jobs have exited. Replace a bridge already in v2 mode with the same namespaced cache view; preserve the exact v2: keys and CAS identities. Do not clear caches or return to legacy readers. Keep explicit v2 mode flags while old bridge images remain possible rollback targets.

Validation: full unit suite (13,141 tests, 199,561 assertions), full static analysis, multi-adapter CI, and released-v2/new-client interoperability covering warm data, invalidation in both directions, state eviction, concurrent writers and stale list fills.

No schema/data migration, extra cache service or production deployment is performed by this release. Previous tags are unchanged.

PR: #1052
Tracking: appwrite-labs/cloud#7152