docs(comments): strip internal task/milestone/bundle bookkeeping from code comments

Remove project bookkeeping citations from shipped code comments across the
solution: hyphenated task IDs (WP-14, StoreAndForward-025), milestone/task/
issue refs (M3, Task 4, Audit Log #23, #21), Bundle X task-bundle labels,
and C/D/K/S/T phase labels.

Comment text only — no code logic, string/log literals, or XML-doc structure
changed. Genuine descriptions are preserved (only the citation is stripped),
and technical lookalikes are retained (UTF-8, SHA-256, T00:00:00, M365,
UTC-5, pre-C4/pre-C5 schema versions). Flagged by the new CommentChecker
TaskReferenceInComment / TrackingReferenceInComment checks plus targeted
grep passes; full solution builds clean, append-only guard tests pass.

src/ZB.MOM.WW.ScadaBridge.SiteEventLogging/EventLogPurgeService.cs

@@ -5,7 +5,7 @@ using Microsoft.Extensions.Options;
 namespace ZB.MOM.WW.ScadaBridge.SiteEventLogging;
 
 /// <summary>
-/// SiteEventLogging-019: predicate the <see cref="EventLogPurgeService"/>
+/// Predicate the <see cref="EventLogPurgeService"/>
 /// consults at the top of every purge tick to decide whether THIS node should
 /// run the daily purge. The design states "a daily background job runs on the
 /// active node and deletes all events older than 30 days"; the standby's local
@@ -40,7 +40,7 @@ public class EventLogPurgeService : BackgroundService
     /// <param name="options">Site event log options (retention days, storage cap, purge interval).</param>
     /// <param name="logger">Logger instance.</param>
     /// <param name="isActiveNode">
-    /// SiteEventLogging-019: optional active-node check. When <c>null</c>, the
+    /// Optional active-node check. When <c>null</c>, the
     /// service runs the purge on every tick (preserves the pre-fix behaviour
     /// for non-clustered hosts and existing tests). When supplied — e.g. by
     /// the Host on a site node — each tick early-exits on the standby so the
@@ -84,7 +84,7 @@ public class EventLogPurgeService : BackgroundService
     {
         try
         {
-            // SiteEventLogging-019: gate every tick on the active-node check.
+            // Gate every tick on the active-node check.
             // The standby's local SQLite receives no writes, so purging there
             // is harmless but unnecessary; the design (Component-SiteEventLogging
             // → Storage) explicitly states the purge runs on the active node.