feat(flow-debugger): FlowStep carries the audit CorrelationId; CLI table adds a correlation column

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

src/ZB.MOM.WW.ScadaBridge.CLI/Commands/FlowDebugTableProjection.cs

@@ -18,7 +18,7 @@ namespace ZB.MOM.WW.ScadaBridge.CLI.Commands;
 /// to the generic renderer unprojected, the object takes the Property/Value branch and the
 /// whole event array lands in one cell as raw JSON. This projects the events through the same
 /// <see cref="FlowGraphBuilder"/> the Flow Debugger page uses and prints one row per STEP —
-/// <c>occurred | kind | lane | target | durationMs | status | lifecycle | error</c> — in the
+/// <c>occurred | kind | lane | target | durationMs | status | lifecycle | correlation | error</c> — in the
 /// order the page draws them, so a terminal user can read the swimlane top-to-bottom. An
 /// outbound operation's rows (a cached call's Submit → Forwarded → Attempted → Resolve, a
 /// notification's Send → Deliver) fold into ONE row whose <c>lifecycle</c> column counts them
@@ -146,6 +146,7 @@ internal static class FlowDebugTableProjection
                 ["durationMs"] = step.DurationMs,
                 ["status"] = status,
                 ["lifecycle"] = lifecycle is { Count: > 0 } ? $"{lifecycle.Count} {(lifecycle.Count == 1 ? "row" : "rows")}" : null,
+                ["correlation"] = step.CorrelationId?.ToString("D"),
                 ["error"] = step.ErrorMessage,
             });
         }