Reject overlapping same-owner deployment claims

[Kewe63]

Summary

• reject a distinct non-sticky deployment claim while an earlier claim from the same actor is active
• keep exact-claim reruns idempotent and preserve legacy lock behavior when no claim ID exists
• regenerate the committed action bundle

Testing

• regression test failed against the previous behavior and passes with the fix
• npm run all
• npm run acceptance (114 scenarios)

Compatibility

Sticky locks and legacy lock records retain their existing owner behavior. The behavior change is limited to distinct overlapping non-sticky claims that would otherwise share cleanup ownership.

Fixes #504

[Kewe63]

@GrantBirki I merged current main into this branch without rewriting history, regenerated the committed bundle from the combined source, and reran the repository validation on Node 24.18.0: npm run all passed (927 tests, 100% line/branch/function coverage) and npm run acceptance passed all 114 scenarios. The PR is conflict-free again at 0798df5. Could you please take another look?