chore(deps): bump ZB.MOM.WW.LocalDb 0.1.3 -> 0.2.1, correct the MaxBatchSize rationale

Closes the pin skew against ScadaBridge (which already pins 0.2.1). Pure pin
bump — no code change was required:

- `RegisterReplicated(string)` still delegates to `baselineExistingRows: false`,
  so `LocalDbSetup.OnReady` is byte-identical in behaviour.
- Everything 0.2.x added is additive (`DeregisterReplicated`, `MaxBatchBytes`,
  the `baselineExistingRows` overload); none of it is called here.
- The wire protocol is unchanged (0.1.x peers still sync) and the on-disk
  bookkeeping schema v1 -> v2 upgrades in place on open, so no rig, volume or
  operator action is needed.

The one thing that DID need reconciling is documentation. 0.2.0 made batching
byte-budgeted: `MaxBatchBytes` (2 MB default, under the 4 MB gRPC cap) now
bounds the wire message, and `MaxBatchSize` is demoted to a secondary row cap
plus the DB read-page size. The rig's `MaxBatchSize = 16` was chosen as a
hand-computed byte proxy ("row-count-only against gRPC's 4 MB cap"), and that
rationale is now wrong everywhere it appeared — appsettings, Configuration.md,
the pair-replication runbook, and both docker-dev site-a services.

The VALUE stays 16, for a different and still-real reason: OplogStore /
SnapshotStreamer materialise a whole read page in memory *before* the
byte-budget split runs, so 16 x ~171 KB artifact chunk rows bounds that
transient allocation at ~2.7 MB. Documented as such, with `MaxBatchBytes`
added to both config tables.

CLAUDE.md records the pin and two deliberate non-adoptions: this repo does not
take ScadaBridge's conditional-registration + boot-time `DeregisterReplicated`
self-heal (OnReady registers all four tables unconditionally, and
LocalDbSetupTests pins that set), and consequently does not use
`baselineExistingRows` either — so enabling replication on a long-running
default-OFF node converges on subsequent writes, not on rows already in the
file. Both are behaviour changes, out of scope for a pin bump.

Verification: solution builds clean; full suite run (57 projects). All 66
LocalDb tests in Host.IntegrationTests green. One unrelated failure,
RoslynVirtualTagEvaluatorTests.Evaluate_racing_ClearCompiledScripts_never_
fails_with_disposed — a Roslyn evaluator disposal race with no LocalDb in its
path, whose own comment documents that its "at most one clear per evaluation"
assumption depends on thread-pool pressure. It passed 3/3 re-runs in isolation
and fails only under full-solution parallel load; pre-existing test-design
fragility, not a regression from this bump.

docker-dev/docker-compose.yml

@@ -660,8 +660,10 @@ services:
       # MUST be byte-identical on both nodes: the interceptor is fail-closed, so any mismatch
       # silently stops the pair converging. NEVER reuse this key outside this local dev rig.
       LocalDb__Replication__ApiKey: "dev-site-a-localdb-sync-key"
-      # Row-count batching against gRPC's 4 MB message cap; artifact chunk rows are ≈171 KB, so
-      # 16 × 171 KB ≈ 2.7 MB stays under the cap with headroom.
+      # Since LocalDb 0.2.0 the WIRE message is bounded by MaxBatchBytes (2 MB default, left
+      # unset), not by this. MaxBatchSize is now the secondary row cap AND the DB read-page size,
+      # and the read page is materialised in memory before the byte-budget split runs — so 16 is
+      # kept to bound that transient allocation (16 × ≈171 KB artifact chunk rows ≈ 2.7 MB).
       LocalDb__Replication__MaxBatchSize: "16"
     ports:
       - "4842:4840"
@@ -728,7 +730,8 @@ services:
       # site-a-2 is the passive half of the replicating pair: it binds the sync listener on 9001
       # but does NOT dial (no PeerAddress). The replication stream is bidirectional, so a-1's
       # single dial carries both directions. Same key + MaxBatchSize as a-1 (byte-identical key
-      # is mandatory — the interceptor fail-closes on a mismatch).
+      # is mandatory — the interceptor fail-closes on a mismatch; MaxBatchSize is now a read-page
+      # bound rather than a byte proxy — see the a-1 comment).
       # Alarm store-and-forward buffer, Phase 2. Enabled on BOTH halves of the pair so the
       # buffer is a live, replicated table rather than an empty one — the live gate needs a real
       # queue to watch converge, and needs to see that only the Primary drains it.