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.

docs/operations/failover-procedures.md

@@ -1,4 +1,4 @@
-# ScadaLink Failover Procedures
+# ScadaBridge Failover Procedures
 
 ## Automatic Failover (No Intervention Required)
 
@@ -105,7 +105,7 @@
 1. Restore SQL Server access.
 2. Central nodes will automatically reconnect (EF Core connection resiliency).
 3. Verify `/health/ready` returns 200.
-4. No manual intervention needed on ScadaLink nodes.
+4. No manual intervention needed on ScadaBridge nodes.
 
 ### Scenario 5: Forced Singleton Migration
 
@@ -113,7 +113,7 @@
 
 **Procedure:**
 1. Initiate graceful shutdown on the degraded node:
-   - Stop the Windows Service: `sc.exe stop ScadaLink-Central`
+   - Stop the Windows Service: `sc.exe stop ScadaBridge-Central`
    - CoordinatedShutdown will migrate singletons to the standby.
 2. Wait for the standby to take over (check logs for "Singleton acquired").
 3. Fix the issue on the original node.