Correlate each onTrigger body await on its own id

[alexanderguy]

Summary

• Each onTrigger body awaitSignal publishes a correlationId on the deployment run's relay SignalAwaited. A delivery completes that park only when the id and the author signal name both match.
• A signal for one correlation does not satisfy a later await of the same name. Two sections may await that name at once. A name-only delivery completes a top-level gate, a deployment-container loop, and a relay park that has no correlation id.
• The admin client lists each live park. One park keeps Approve. Several parks are chosen by step, and a correlated park is posted with its correlationId. Delivery still requires manage on the deployment run.

Verification

• gmake all WF_PARALLEL=2 exits 0 (lint, tsc -b, the admin UI bundle, unit tests, the workflow-deploy suite, and hub/db tests). Two live Google GenAI tests skip.
• The workflow-deploy suite shows a name-only delivery leaving a new onTrigger park waiting, the matching correlation completing it, a late correlation leaving the next turn, two sections receiving separate deliveries, and a name-only delivery completing a top-level gate beside a section.

Closes INTR-402

[alexanderguy]

Self-review (code-review skill) returned clean.

[linear]

INTR-402