feat(localdb): alarm_sf_events replicated table

Adds the alarm store-and-forward buffer to the consolidated LocalDb file and
registers it for replication, so a node that dies with undelivered alarm
history no longer takes it to the grave.

The table keeps the legacy queue's shape rather than the status column the
plan sketched. An acknowledged row is deleted, not marked delivered: that
needs no second sweeper to keep the table bounded, leaves the capacity
semantics untouched, and the replication engine carries the delete as a
tombstone so the peer drops its copy anyway -- which is what the status
column was for. last_error is retained because it is the only operator-facing
record of why a row was dead-lettered.

The primary key is app-minted TEXT. The legacy AUTOINCREMENT RowId cannot
replicate under last-writer-wins: two nodes would independently allocate
rowid 7 to different alarms and silently overwrite each other. The drain
index therefore orders by enqueued_at_utc rather than insertion order, with
id as a tiebreak so the ordering is total.

Tables are created unconditionally, independent of AlarmHistorian:Enabled.
An empty registered table costs three triggers; creating it lazily would mean
a node that enables the historian later writes rows before its capture
triggers exist, which is exactly the silent-loss shape OnReady's ordering
comment warns about.

Claude-Session: https://claude.ai/code/session_01GASWkNEi68FSCtvr6rLoEW

src/Server/ZB.MOM.WW.OtOpcUa.Host/Configuration/LocalDbSetup.cs

@@ -1,11 +1,12 @@
 using ZB.MOM.WW.LocalDb;
+using ZB.MOM.WW.OtOpcUa.Core.AlarmHistorian;
 using ZB.MOM.WW.OtOpcUa.Runtime.DeploymentCache;
 
 namespace ZB.MOM.WW.OtOpcUa.Host.Configuration;
 
 /// <summary>
-///     The <c>onReady</c> callback handed to <c>AddZbLocalDb</c>: creates the deployment-cache
-///     tables and opts them into replication.
+///     The <c>onReady</c> callback handed to <c>AddZbLocalDb</c>: creates the deployment-cache and
+///     alarm store-and-forward tables and opts them into replication.
 /// </summary>
 /// <remarks>
 ///     <para>
@@ -26,8 +27,15 @@ public static class LocalDbSetup
     ///         <c>RegisterReplicated</c> is what installs the three AFTER triggers that capture
     ///         changes into the oplog. Any row written before that call is never captured, so it
     ///         never reaches the peer — silently, and permanently, because nothing ever revisits
-    ///         history. Phase 1 writes nothing here; when Phase 2 adds its store-and-forward
-    ///         migrator, the migrator must run <i>after</i> both registrations for the same reason.
+    ///         history. The Phase-2 legacy alarm migrator therefore runs <i>after</i> every
+    ///         registration, not alongside the DDL.
+    ///     </para>
+    ///     <para>
+    ///         The alarm buffer's tables are created unconditionally, regardless of whether this
+    ///         node has <c>AlarmHistorian:Enabled</c> set. An empty registered table costs three
+    ///         triggers and nothing else, whereas creating it lazily when the sink first appears
+    ///         would mean a node that enables the historian later writes rows before its triggers
+    ///         exist — which is precisely the silent-loss shape above.
     ///     </para>
     /// </remarks>
     /// <param name="db">The freshly constructed local database.</param>
@@ -40,9 +48,11 @@ public static class LocalDbSetup
         using (var connection = db.CreateConnection())
         {
             DeploymentCacheSchema.Apply(connection);
+            AlarmSfSchema.Apply(connection);
         }
 
         db.RegisterReplicated(DeploymentCacheSchema.ArtifactsTable);
         db.RegisterReplicated(DeploymentCacheSchema.PointerTable);
+        db.RegisterReplicated(AlarmSfSchema.EventsTable);
     }
 }