fix(harness): make deploy E2E tests pass against real SQL (seed cluster FKs)

Integration-sweep follow-up #6 (SQL leg). The sweep flagged 7 heavy 2-node
deploy/failover/reconnect E2E tests as 'time out under amd64-emulated SQL' and
suggested raising deadlines. That diagnosis was WRONG: run against real
(native-amd64) SQL on the Docker host, they still hang — even at 4x deadline.
Root cause is that these tests had never actually run against real SQL, only the
EF in-memory provider, which does NOT enforce foreign keys.

Two distinct defects, both hidden by in-memory:

1. Missing FK-parent seed (5 tests). The deploy records a NodeDeploymentState row
   per node, FK'd to ClusterNode (FK_NodeDeploymentState_ClusterNode_NodeId). The
   tests never seeded ServerCluster + ClusterNode, so on SQL each node-state INSERT
   throws and the deploy never seals (waits the full deadline regardless of size).
   Added TwoNodeClusterHarness.SeedDefaultClusterAsync (seeds a ServerCluster +
   a ClusterNode per node; Warm/NodeCount=2 to satisfy the SQL CHECK constraint
   CK_ServerCluster_RedundancyMode_NodeCount AND the ClusterEnabledNodeCountMismatch
   validator). Called it in DeployHappyPath x2 / Failover / FleetDiagnostics /
   EquipmentNamespace; fixed DriverReconnect to seed node B + NodeCount=2.

2. Stale EquipmentId (EquipmentNamespace test; pre-existing on BOTH providers).
   Seeded EquipmentId='eq-1', but the later-added EquipmentIdNotDerived validator
   requires EquipmentId == DeriveEquipmentId(EquipmentUuid) ('EQ-'+first 12 hex).
   Fixed the seed to a canonical id + matching UUID. Only surfaced once the FK fix
   let the deploy reach equipment validation.

Also added OTOPCUA_HARNESS_SQL_HOST / OTOPCUA_HARNESS_LDAP_HOST overrides so the
harness fixtures can run on the native-amd64 Docker host (avoids arm64 mssql
emulation entirely).

Verified: the 5 SQL-backed classes go 11/11 green vs native SQL; in-memory default
unregressed (12/12). RoslynVirtualTagEvaluatorTests racing test is a pre-existing
flaky race (not SQL-backed; passes in isolation) — left as-is.

tests/Server/ZB.MOM.WW.OtOpcUa.Host.IntegrationTests/DriverReconnectE2eTests.cs

@@ -218,8 +218,10 @@ public sealed class DriverReconnectE2eTests
             Name = "Reconnect E2E Cluster",
             Enterprise = "zb",
             Site = "central",
-            NodeCount = 1,
-            RedundancyMode = RedundancyMode.None,
+            // Both harness nodes are Enabled driver members, so NodeCount must be 2 (Warm) to
+            // satisfy the ClusterEnabledNodeCountMismatch validator + the SQL CHECK constraint.
+            NodeCount = 2,
+            RedundancyMode = RedundancyMode.Warm,
             CreatedBy = "test",
         });
 
@@ -240,6 +242,18 @@ public sealed class DriverReconnectE2eTests
             CreatedBy = "test",
         });
 
+        // The harness runs BOTH nodes as driver members, so the deployment records a
+        // NodeDeploymentState for node B too — seed its ClusterNode row so the real-SQL FK
+        // (FK_NodeDeploymentState_ClusterNode_NodeId) resolves. (In-memory ignores FKs.)
+        db.ClusterNodes.Add(new ClusterNode
+        {
+            NodeId = harness.NodeBNodeId,
+            ClusterId = ClusterId,
+            Host = TwoNodeClusterHarness.LoopbackHost,
+            ApplicationUri = "urn:zb:reconnect-e2e:node-b",
+            CreatedBy = "test",
+        });
+
         db.DriverInstances.Add(new DriverInstance
         {
             DriverInstanceId = DriverId,