Add summary to side effect and mutable side effect

[Quinn-With-Two-Ns]

Add summary to side effect and mutable side effect.

closes #2702

---

Note

Add summary options to side/mutable side effects and plumb user metadata into marker/events across runtime, with API overloads and tests verifying metadata.

• API/SDK:
  • Add SideEffectOptions and MutableSideEffectOptions with summary support.
  • Overload Workflow.sideEffect(..) and mutableSideEffect(..) (and outbound interceptor methods) to accept options.
  • Propagate summaries as UserMetadata for timers, side effects, mutable side effects, child workflows, local activities, and Nexus operations.
• State Machines/Runtime:
  • Pass UserMetadata through SideEffectStateMachine and MutableSideEffectStateMachine; attach to RECORD_MARKER commands.
  • Extend StateMachineCommandUtils.createRecordMarker to accept optional metadata; update callers.
  • Wire metadata through ReplayWorkflowContext, WorkflowStateMachines, and SyncWorkflowContext.
• Tests/Utilities:
  • Add and use HistoryUtils.assertEventMetadata.
  • Update unit/integration tests to verify marker/event metadata for side effects, mutable side effects, activities, local activities, child workflows, and Nexus operations.
  • Update tracing/dummy/test contexts to support new overloads.

^{Written by Cursor Bugbot for commit f0cafac. This will update automatically on new commits. Configure here.}

[yuandrew]

LGTM, minor doc comments

[yuandrew]

For my own understanding, why do we null after recording once? Is it because replay is the only time we'd re-create a marker, and we don't need this for replay?

[Quinn-With-Two-Ns]

Otherwise we just hold the metadata in memory when we no longer need it, just a memory optimization.