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/requirements/Component-ClusterInfrastructure.md

@@ -24,10 +24,10 @@ This component is a **design responsibility**, not a single buildable project th
 contains all of the code. The cluster-infrastructure responsibilities above are
 realised across two projects:
 
-- **`src/ScadaLink.ClusterInfrastructure`** owns the cluster **configuration model**:
+- **`src/ZB.MOM.WW.ScadaBridge.ClusterInfrastructure`** owns the cluster **configuration model**:
   the `ClusterOptions` POCO (seed nodes, roles, remoting/gRPC ports, failure-detection
   timings, split-brain settings) bound from `appsettings.json` via the Options pattern.
-- **`src/ScadaLink.Host`** owns the cluster **bootstrap and runtime wiring**: it
+- **`src/ZB.MOM.WW.ScadaBridge.Host`** owns the cluster **bootstrap and runtime wiring**: it
   builds the Akka.NET HOCON from `ClusterOptions`, starts the `ActorSystem`,
   configures the keep-oldest split-brain resolver (`down-if-alone = on`), wires
   `CoordinatedShutdown` into the service lifecycle, and provides active-node /