Handle duplicate publishing needlessly failing

[jpwilliams]

Summary

Fixes the release process failing if a package is already published on npm; this should just continue as normal, as these may be released by humans or other actions.

Checklist

• [ ] ~Added a docs PR that references this PR~ N/A CI fix
• [ ] ~Added unit/integration tests~ N/A CI fix
• [x] Added changesets if applicable

Related

• Clean-up following borked release in #725 - should ensure this doesn't happen again

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 9030359fd4c4be6bc7768e5d10e08429f0427a86

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR