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.Commons/Entities/Schemas/SharedSchema.cs

@@ -1,10 +1,10 @@
 namespace ZB.MOM.WW.ScadaBridge.Commons.Entities.Schemas;
 
 /// <summary>
-/// A reusable, named JSON-Schema library entry (M9 template-level JSON-Schema library,
-/// Task T32a). Schemas are referenced from inbound-API / template schema definitions via a
-/// <c>{"$ref":"lib:Name"}</c> pointer resolved against this library (the resolver lands in
-/// T32b). One row per named schema in the central <c>SharedSchemas</c> MS SQL table.
+/// A reusable, named JSON-Schema library entry (template-level JSON-Schema library).
+/// Schemas are referenced from inbound-API / template schema definitions via a
+/// <c>{"$ref":"lib:Name"}</c> pointer resolved against this library. One row per
+/// named schema in the central <c>SharedSchemas</c> MS SQL table.
 /// </summary>
 /// <remarks>
 /// Persistence-ignorant POCO; the EF Core mapping lives in the Configuration Database