fix(historian): correct AlarmHistorian config-key refs in docs + install (review)

docs/drivers/Historian.Wonderware.md

@@ -4,7 +4,7 @@ The Wonderware Historian backend is **not a tag driver** — it has no address
 space, no `IDriver` lifecycle, and exposes no PLC. It is a **server-side
 historian sink**: an optional sidecar that gives OtOpcUa read access to AVEVA
 System Platform (Wonderware) Historian history and a write-back path for alarm
-events. It runs only when `Historian:Wonderware:Enabled=true`.
+events. It runs only when `AlarmHistorian:Enabled=true`.
 
 The host connects to the sidecar over **TCP** (plaintext in dev, optional TLS
 in prod), so the OtOpcUa host no longer needs to be on the same machine as the
@@ -55,7 +55,7 @@ Set `OTOPCUA_HISTORIAN_TLS_ENABLED=true` on the sidecar and supply the server
 certificate via `OTOPCUA_HISTORIAN_TLS_CERT` (PFX file path, or
 `LocalMachine\My\<thumbprint>` for a cert already in the machine store) and
 `OTOPCUA_HISTORIAN_TLS_CERT_PASSWORD` if the PFX is password-protected. On the
-client/host side set `Historian:Wonderware:UseTls=true`; optionally set
+client/host side set `AlarmHistorian:UseTls=true`; optionally set
 `ServerCertThumbprint` to pin the server certificate's SHA-1 thumbprint instead
 of relying on normal CA-chain validation.