Feat/irokle: Replace automerge and gossip with a performance optimized version of irokle

[St4NNi]

This PR replaces the legacy Automerge/gossip-based metadata synchronization path with an irokle-backed document sync pipeline. It also hardens metadata replication with durable task/outbox persistence, improves cold-start recovery, and adds performance work across metadata materialization, and storage read / list operations.

Changes

• Replace the legacy Automerge and gossip runtime with irokle-backed document synchronization for core metadata documents, realm configuration, and lifecycle events.
• Add durable document sync outboxes, persistent task scheduling, failed-task rearming, and startup restoration so metadata sync work survives restarts and transient failures.
• Introduce realm-scoped sync placements, peer refresh/backfill logic, and node/topic diagnostics to make replication targets explicit and easier to inspect.
• Rework metadata handling around event-sourced updates, deterministic actors, materialization queues, visible registry caching, and cache warming to reduce read-time work and improve convergence behavior.
• Improve listing and storage performance with batched point reads, inclusive iterator start bounds, faster hash path handling, visible registry lookups, and ListObjectsV2 pagination/common-prefix optimizations.
• Add stage, latency, queue-lag, DHT lookup, and replication telemetry to make sync throughput, tail latency, and backlog behavior observable during operation and tests.
• Drastically improve performance by batching operations and reducing IO churn
• Expand API support and tests around users, groups, info endpoints, onboarding, metadata CRUD, replication, cold starts, throughput, convergence tails, and query concurrency.
• Update dependencies, doctor tooling, startup wiring, and diagnostics to support the new irokle-based sync architecture end to end.

[das-Abroxas]

Unfortunately, it is not possible to review a pull request of this size in all its extent within a reasonable amount of time. However, I hope that the tests implemented in Aruna with this (as well as the tests in Craqle and Irokle) provide sufficient evidence of the stability and consistency of this implementation. For the most part, I have to trust your judgement here and assume that you know what you're doing and that hopefully you'll take responsibility whatever the outcome.