feat(mesh-phase5): tap the 4 telemetry publish seams into the local hub (DPS intact)

Each of the four telemetry publish seams now also emits its DPS payload into the
node-local ITelemetryLocalHub (Phase 5), leaving the existing DistributedPubSub
publish untouched:

- driver-health   AkkaDriverHealthPublisher            -> TelemetryItem.Health
- resilience      DriverResilienceStatusPublisherService -> TelemetryItem.Resilience
- alerts          ScriptedAlarmHostActor + DriverHostActor (native) -> TelemetryItem.Alarm
- script-logs     VirtualTagActor + DpsScriptLogPublisher -> TelemetryItem.Script

DI services take the hub as a required ctor param; actors take an optional
nullable hub threaded through their Props and the real spawn sites
(DriverHostActor <- ServiceCollectionExtensions; VirtualTagActor/ScriptedAlarmHostActor
<- DriverHostActor), so existing test Props constructions keep compiling and simply
do not emit. The hub is a no-op until a gRPC client subscribes, so the emit is safe
on every node.

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

src/Server/ZB.MOM.WW.OtOpcUa.Runtime/ServiceCollectionExtensions.cs

@@ -495,7 +495,11 @@ public static class ServiceCollectionExtensions
                     replicationPeerHost: replicationPeerHost,
                     fetchAndCacheMode: fetchAndCacheMode,
                     artifactFetcher: artifactFetcher,
-                    alarmStateStore: alarmStateStore),
+                    alarmStateStore: alarmStateStore,
+                    // Phase 5: the node-local live-telemetry hub (registered in AddOtOpcUaRuntime). The host
+                    // emits its Primary-gated native-alarm transitions into it and threads it into the
+                    // VirtualTag + ScriptedAlarm hosts it spawns.
+                    telemetryHub: resolver.GetService<ITelemetryLocalHub>()),
                 DriverHostActorName);
             registry.Register<DriverHostActorKey>(driverHost);