test(v3-batch4): add Calculation to the driver-probe idempotency key set

Pre-existing stale test surfaced by Batch 4's full gate (Batch 2/3 gates were
live-/run and never ran Host.IntegrationTests): Batch 2 registered CalculationProbe
in DriverFactoryBootstrap (9 probes) but AddOtOpcUaDriverProbes_is_idempotent's
AdminUiDriverTypeKeys still listed 8, so distinctTypes(9) != Length(8). Calculation
is a real DriverTypeNames.Calculation pseudo-driver with a probe; add it and refresh
the now-stale *DriverPage.razor comment (that routed flow retired in Batch 2). Not a
Batch-4 code change — a test-correctness fix.

Claude-Session: https://claude.ai/code/session_01LVneM3eh1UtJxEisFXgmox

tests/Server/ZB.MOM.WW.OtOpcUa.Host.IntegrationTests/DriverProbeRegistrationTests.cs

@@ -17,8 +17,10 @@ namespace ZB.MOM.WW.OtOpcUa.Host.IntegrationTests;
 public sealed class DriverProbeRegistrationTests
 {
     // The canonical "all drivers" set — one entry per AdminUI typed driver page's DriverTypeKey.
-    // Keep in sync with the DriverTypeKey constants in
-    // src/Server/.../Components/Pages/Clusters/Drivers/*DriverPage.razor.
+    // Keep in sync with the IDriverProbe registrations in
+    // src/Server/.../Host/Drivers/DriverFactoryBootstrap.AddOtOpcUaDriverProbes (the routed
+    // *DriverPage.razor flow was retired in v3 Batch 2 — the driver-type keys now live in the /raw
+    // modals, but the probe set is the authority for what the AdminUI can Test-connect).
     private static readonly string[] AdminUiDriverTypeKeys =
     [
         "Modbus",
@@ -29,6 +31,7 @@ public sealed class DriverProbeRegistrationTests
         "Focas",                 // page key; probe reports "FOCAS"  — must resolve case-insensitively
         "OpcUaClient",
         "GalaxyMxGateway",
+        "Calculation",           // v3 Batch 2 pseudo-driver; CalculationProbe registered in DriverFactoryBootstrap
     ];
 
     [Fact]