docs(src): fix CommentChecker findings across src/ — 1,032 → 5 (all false positives)

Comment/XML-doc changes only, no code logic:
- strip project-tracking references (WP*, P*-*, row-NN, #NN, Task N) from
  comments, keeping the explanatory rationale
- add missing summaries, <param>, <returns>, <typeparam> and <inheritdoc/>
- replace misused <inheritdoc/> with real docs; where <inheritdoc/> was
  combined with useful remarks, move the rationale into // comments
- drop stale replicationActor <param> on DeploymentManagerActor ctor

Remaining 5 are false positives (CWE-1236 x2, failures-1, year-0001, M365).
Build 0 errors / 0 warnings.

src/ZB.MOM.WW.ScadaBridge.Communication/Grpc/CentralControlGrpcService.cs

@@ -277,21 +277,15 @@ public sealed class CentralControlGrpcService : CentralControlService.CentralCon
         return CentralControlDtoMapper.ToDto(ack);
     }
 
-    /// <summary>
-    /// Application heartbeat — <b>always answers OK</b>, even when this node is not ready.
-    /// </summary>
-    /// <remarks>
-    /// The heartbeat is fire-and-forget on both sides: nothing on the site consumes the reply,
-    /// and the site's heartbeat timer must never take a fault (a failing heartbeat that raised
-    /// an error would be a self-inflicted outage on a purely informational signal). So this is
-    /// the one RPC that does not go through <see cref="RequireReady"/>: a heartbeat arriving
-    /// before the actor exists is logged and dropped, exactly as the actor itself drops one
-    /// that arrives before <c>ICentralHealthAggregator</c> is resolvable. Liveness is still
-    /// detected — the aggregator's offline timeout fires when the heartbeats stop landing.
-    /// </remarks>
-    /// <param name="request">The heartbeat.</param>
-    /// <param name="context">The gRPC call context.</param>
-    /// <returns>An empty reply, always.</returns>
+    // Application heartbeat — always answers OK, even when this node is not ready.
+    // The heartbeat is fire-and-forget on both sides: nothing on the site consumes the reply,
+    // and the site's heartbeat timer must never take a fault (a failing heartbeat that raised
+    // an error would be a self-inflicted outage on a purely informational signal). So this is
+    // the one RPC that does not go through RequireReady: a heartbeat arriving before the actor
+    // exists is logged and dropped, exactly as the actor itself drops one that arrives before
+    // ICentralHealthAggregator is resolvable. Liveness is still detected — the aggregator's
+    // offline timeout fires when the heartbeats stop landing.
+    /// <inheritdoc />
     public override Task<Empty> Heartbeat(HeartbeatDto request, ServerCallContext context)
     {
         var central = _central;