refactor: rename ScadaLink → ZB.MOM.WW.ScadaBridge (code + projects + namespaces)

Solution + 23 src projects + 26 test projects renamed; folders, csproj,
namespaces, and ScadaLinkDbContext/ScadaBridgeDbContext class updated.
ActorSystem "scadalink" → "scadabridge", Akka seed-node URLs migrated.
SQL roles/logins, LDAP domains, CLI command name, and CLI config dir
(~/.scadalink → ~/.scadabridge) also renamed.

Build green; 5 Host.Tests fail awaiting SQL login rename in next commit.
Pre-existing StaleTagMonitor timing flakes unchanged.

Rename script committed at tools/rename-to-scadabridge.sh.

src/ZB.MOM.WW.ScadaBridge.InboundAPI/IActiveNodeGate.cs

@@ -0,0 +1,24 @@
+namespace ZB.MOM.WW.ScadaBridge.InboundAPI;
+
+/// <summary>
+/// InboundAPI-008: abstraction the inbound API endpoint uses to determine whether
+/// this node is the active (cluster-leader) central node.
+///
+/// The design states the inbound API is "Central cluster only (active node)" and
+/// "fails over with it". A standby central node must not execute method scripts or
+/// <c>Route.To()</c> calls — that can race the active node or run against stale
+/// singleton state. <see cref="InboundApiEndpointFilter"/> consults this gate and
+/// returns HTTP 503 from a standby so Traefik/clients only reach the live node.
+///
+/// The implementation lives in the Host (it needs Akka cluster state); when no
+/// implementation is registered, the endpoint defaults to "allow" so non-clustered
+/// hosts and tests are unaffected.
+/// </summary>
+public interface IActiveNodeGate
+{
+    /// <summary>
+    /// <c>true</c> when this node is the active central node and may serve the
+    /// inbound API; <c>false</c> on a standby node.
+    /// </summary>
+    bool IsActiveNode { get; }
+}