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.StoreAndForward/IStoreAndForwardSiteContext.cs

@@ -0,0 +1,27 @@
+namespace ZB.MOM.WW.ScadaBridge.StoreAndForward;
+
+/// <summary>
+/// Optional ambient site context the Store-and-Forward service consults at
+/// construction time. Carries the site identifier the S&amp;F retry loop
+/// stamps onto cached-call audit telemetry (Audit Log #23 / M3 Bundle F).
+/// </summary>
+/// <remarks>
+/// <para>
+/// Defined here (not in <c>HealthMonitoring</c> alongside the existing
+/// <c>ISiteIdentityProvider</c>) so the dependency arrow does not flip:
+/// <c>HealthMonitoring</c> already references <c>StoreAndForward</c>, and
+/// having S&amp;F take a dependency on <c>HealthMonitoring</c> would create a
+/// project-reference cycle.
+/// </para>
+/// <para>
+/// The Host registers a trivial adapter that forwards to the same
+/// <c>NodeOptions.SiteId</c> the existing <c>ISiteIdentityProvider</c> reads.
+/// Resolution is optional: when no binding is registered the S&amp;F service
+/// stamps an empty site id, preserving the legacy pre-M3 behaviour exactly.
+/// </para>
+/// </remarks>
+public interface IStoreAndForwardSiteContext
+{
+    /// <summary>The site id stamped onto cached-call audit telemetry.</summary>
+    string SiteId { get; }
+}