refactor: scrub residual ScadaLink refs → ScadaBridge (env vars, config keys, assembly name, SQL login)

Renames the 13 SCADALINK_* runtime env vars → SCADABRIDGE_*, the ScadaLink__
.NET config keys → ScadaBridge__, the stale ScadaLink.Host.exe assembly name
→ ZB.MOM.WW.ScadaBridge.Host.exe, the scadalink_app SQL login → scadabridge_app,
and residual identifiers/comments/docs. Migration records (prior rename
tooling/design, DB-rename helper, this scrub script) carved out.

Adds tools/scrub-scadalink-refs.sh.

docs/requirements/Component-CLI.md

@@ -310,9 +310,9 @@ Configuration is resolved in the following priority order (highest wins):
 
 1. **Command-line options**: `--url`, `--username`, `--password`, `--format`.
 2. **Environment variables**:
-   - `SCADALINK_MANAGEMENT_URL` — Management API URL (e.g., `http://central-host:5000`).
-   - `SCADALINK_FORMAT` — Default output format (`json` or `table`).
-   - `SCADALINK_USERNAME` / `SCADALINK_PASSWORD` — LDAP credentials. Preferred over
+   - `SCADABRIDGE_MANAGEMENT_URL` — Management API URL (e.g., `http://central-host:5000`).
+   - `SCADABRIDGE_FORMAT` — Default output format (`json` or `table`).
+   - `SCADABRIDGE_USERNAME` / `SCADABRIDGE_PASSWORD` — LDAP credentials. Preferred over
      `--password` on the command line, which is visible in process listings and shell
      history. Credentials are never read from the config file.
 3. **Configuration file**: `~/.scadabridge/config.json` — Persistent defaults for management URL and output format only (never credentials).

docs/requirements/Component-Transport.md

@@ -53,7 +53,7 @@ Exactly one of `content.json` or `content.enc` is present.
   "createdAtUtc": "2026-05-24T12:34:56Z",
   "sourceEnvironment": "dev-cluster-a",
   "exportedBy": "alice@corp.example",
-  "scadaLinkVersion": "1.4.2",
+  "scadaBridgeVersion": "1.4.2",
   "contentHash": "sha256:...",
   "encryption": {
     "algorithm": "AES-256-GCM",
@@ -325,7 +325,7 @@ The `manifest.json` file is always present in the ZIP root and is never encrypte
   "createdAtUtc": "2026-05-24T12:34:56Z",
   "sourceEnvironment": "dev-cluster-a",
   "exportedBy": "alice@corp.example",
-  "scadaLinkVersion": "1.4.2",
+  "scadaBridgeVersion": "1.4.2",
   "contentHash": "sha256:abc123...",
   "encryption": {
     "algorithm": "AES-256-GCM",
@@ -371,7 +371,7 @@ The `manifest.json` file is always present in the ZIP root and is never encrypte
 | `createdAtUtc` | ISO-8601 UTC timestamp of when the export was created. |
 | `sourceEnvironment` | The `SourceEnvironment` name of the exporting cluster (from `TransportOptions`). Displayed in the import wizard and required to be retyped at the confirm step. |
 | `exportedBy` | Authenticated username of the person who performed the export. |
-| `scadaLinkVersion` | Application version of the exporting node. Used for diagnostic display only. |
+| `scadaBridgeVersion` | Application version of the exporting node. Used for diagnostic display only. |
 | `contentHash` | `sha256:<hex>` — SHA-256 of the raw `content.json` or `content.enc` bytes (pre-encryption). Verified on upload before any decryption. |
 | `encryption` | Present only when a passphrase was supplied. Contains the KDF parameters and the per-bundle random salt and IV needed to re-derive the key and decrypt. Omitted for plaintext bundles. |
 | `encryption.algorithm` | Always `"AES-256-GCM"` in v1. |

docs/requirements/HighLevelReqs.md

@@ -531,7 +531,7 @@ Sites log operational events locally, including:
 - The CLI sends user credentials via HTTP Basic Auth. The server authenticates against **LDAP/AD** and resolves roles before dispatching commands to the ManagementActor.
 - CLI commands mirror all Management Service operations: templates, instances, sites, data connections, deployments, external systems, notifications, security (API keys and role mappings), audit log queries, and health status.
 - Output is **JSON by default** (machine-readable, suitable for scripting) with an optional `--format table` flag for human-readable tabular output.
-- Configuration is resolved from command-line options, **environment variables** (`SCADALINK_MANAGEMENT_URL`, `SCADALINK_FORMAT`), or a **configuration file** (`~/.scadabridge/config.json`).
+- Configuration is resolved from command-line options, **environment variables** (`SCADABRIDGE_MANAGEMENT_URL`, `SCADABRIDGE_FORMAT`), or a **configuration file** (`~/.scadabridge/config.json`).
 - The CLI is a separate executable from the Host binary — it is deployed on any machine with HTTP access to a central node.
 
 ## 14. General Conventions