fix(core-scripted-alarms): resolve Low code-review findings (Core.ScriptedAlarms-003,006,008,010,011; -009 documented)

- Core.ScriptedAlarms-003: emit OnEvent OUTSIDE _evalGate by collecting
  pending emissions during the gate-held section and flushing them after
  release; eliminates re-entrancy deadlock the docs already promised.
- Core.ScriptedAlarms-006: track every fire-and-forget Reevaluate /
  ShelvingCheck task in _inFlight; Dispose drains the set so the engine
  no longer races store writes against teardown.
- Core.ScriptedAlarms-008: store comments as ImmutableList<AlarmComment>
  so AppendComment is O(log n) instead of O(n).
- Core.ScriptedAlarms-010: document the deliberate input-quality
  asymmetry (Uncertain drives the predicate, renders {?} in the message)
  in docs/ScriptedAlarms.md and on MessageTemplate.Resolve remarks.
- Core.ScriptedAlarms-011: propagate the no-op reason through
  TransitionResult.NoOp(state, reason) and log it from
  ScriptedAlarmEngine.ApplyAsync.
- Core.ScriptedAlarms-009 (Won't Fix per recommendation): documented the
  per-evaluation dictionary allocation in docs/v2/Galaxy.Performance.md
  with a mitigation path if a future soak surfaces pressure.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

src/Core/ZB.MOM.WW.OtOpcUa.Core.ScriptedAlarms/MessageTemplate.cs

@@ -33,6 +33,16 @@ public static class MessageTemplate
     ///     has a non-Good <see cref="DataValueSnapshot.StatusCode"/> or a null
     ///     <see cref="DataValueSnapshot.Value"/> resolve to <c>{?}</c>.
     /// </summary>
+    /// <remarks>
+    ///     Quality bar is intentionally <em>stricter</em> than predicate evaluation:
+    ///     only Good (StatusCode == 0) is substituted; Uncertain renders as
+    ///     <c>{?}</c>. The predicate gate (<c>ScriptedAlarmEngine.AreInputsReady</c>)
+    ///     accepts Uncertain because it still carries a value the predicate can
+    ///     inspect, but the operator-facing message must make doubt explicit rather
+    ///     than substituting a value an operator might act on. See the
+    ///     "Input-quality policy" section in <c>docs/ScriptedAlarms.md</c>.
+    ///     (Core.ScriptedAlarms-010)
+    /// </remarks>
     public static string Resolve(string template, Func<string, DataValueSnapshot?> resolveTag)
     {
         if (string.IsNullOrEmpty(template)) return template ?? string.Empty;