ci: separate publish workflow to ensure order

[holic]

moves our npm publish step to a single workflow that calls out to the previous workflows, but with needs to ensure order of operations

noticed that we had both "snapshot" and "release" CI steps running simultaneously, where "snapshot" would sometimes run first (due to concurrency), which would publish a new npm version for a release but not properly tag+release on github

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 5df277da8f03596318864e4e09b11c9f1769d677

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