🐛 Bug: Releases can become broken after two quick pushes to main

[JoshuaKGoldberg]

Bug Report Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Expected

Back in #556 I'd requested changing the release workflow to cancel-in-progress: true. The idea was that if they were running in series, later workflows wouldn't have up-to-date commits from main. I'd thought this would fix the checked-in version to always be in sync with what was published to npm.

The general flow is meant to be:

1. Commit A is pushed
2. Commit A's release flow starts
3. Commit A's release is published to npm
4. Commit A's Git commit is pushed to GitHub
5. Commit A's release flow finishes
6. ...some time later
7. Commit B is pushed
8. etc.

Actual

Unfortunately, there's still a race condition. Take the following order:

1. Commit A is pushed
2. Commit A's release flow starts
3. Commit A publishes to npm
4. Commit B is pushed
5. Commit B's release flow starts
6. Commit A's release flow is canceled

Note that Commit A's Git commit was never pushed to GitHub.

Additional Info

Example CI failure: https://github.com/JoshuaKGoldberg/create-typescript-app/actions/runs/6262715180/job/17005549976

npm notice === Tarball Details === 
npm notice name:          create-typescript-app                   
npm notice version:       1.30.0                                  
npm notice filename:      create-typescript-app-1.30.0.tgz        
npm notice package size:  101.4 kB                                
npm notice unpacked size: 379.1 kB                                
npm notice shasum:        4a38a5622710939ba6aa9cd66dbd8f3ba3f922a9
npm notice integrity:     sha512-Oq4LkNynwxKmH[...]fMZaQDqiHR+fA==
npm notice total files:   262                                     
npm notice 
npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=37720651
npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/create-typescript-app - You cannot publish over the previously published versions: 1.30.0.
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.

Looks like https://github.com/orgs/community/discussions/12835 discusses proposals for a built-in way to avoid this classification of issue.

[github-actions]

🎉 This is included in version v1.32.0 🎉

The release is available on:

• GitHub releases
• npm package (@latest dist-tag)

Cheers! 📦🚀