Queue Swift releases and drop the stale onde checkout
The release workflow had no concurrency group at all, so a re-pushed tag or a dispatch fired during a tag run starts a second 2h20m macOS build next to the first, with both racing to push a commit and a tag to ed-swift. Runs now queue per ref. They deliberately do not cancel: killing a run between "create the GitHub release" and "push to ed-swift" leaves a release with no assets attached to it. 98cdf9b moved Ed off the onde path dependency and onto the published crate, which left the sibling checkout in all three jobs cloning the engine for nothing, and left ONDE_REF claiming to pick the onde revision CI builds against when it no longer picks anything. To build Ed against an unreleased onde, add a [patch.crates-io] entry pointing at the sibling path instead. Co-Authored-By: siGit Code <noreply@sigit.si>