Correlate remote publisher runs by release identifier

[DariuszPorowski]

Parent: #11777

Implementation plan: PR 10 — Release-identifier correlation for remote dispatch

Design: GoReleaser Release Lifecycle

Implementation PR: #12783

Companion PR: azure-octo/radius-publisher#25, which must merge and deploy first.

Scope

Carry a stable <version>-<source-sha> identifier through Deployment Engine and Bicep publisher dispatches. Match remote runs by that identifier, query before dispatch to prevent duplicates, and remove time-window correlation. Update publisher run names and concurrency groups in the companion repository.

Acceptance criteria

• Concurrent dispatches correlate only to their own remote runs.
• Retries reuse successful or active work and reconcile uncertain dispatch outcomes.
• The publisher companion PR is merged and deployed before the Radius PR.
• Implementation PR ci(refactor-release): correlate publisher runs by release identifier #12783 is merged.