feat(cluster): AllowSingleNodeCluster flag — single-seed installs drop the phantom seed

Validator lowers the seed-count floor to 1 when AllowSingleNodeCluster is set,
otherwise still requires 2 and points operators at the flag. The plan's
deploy/wonder-app-vd03/appsettings.Central.json edit is skipped: that production
deploy artifact is not tracked in this repo (only its deployment record doc is).

src/ZB.MOM.WW.ScadaBridge.ClusterInfrastructure/ClusterOptions.cs

@@ -76,4 +76,12 @@ public class ClusterOptions
     /// other reachable members, rather than running as an isolated single-node cluster.
     /// </summary>
     public bool DownIfAlone { get; set; } = true;
+
+    /// <summary>
+    /// Acknowledges a deliberate single-node deployment: permits exactly one seed
+    /// node (normally ≥2 are required so either node can start first). Without this
+    /// flag a single-node install must list a phantom second seed, which the node
+    /// dials forever — log noise and a defeated validation intent (review 01).
+    /// </summary>
+    public bool AllowSingleNodeCluster { get; set; }
 }