Better way of handling NPM releases and package.json versioning

[dylanyoung-dev]

Would love to avoid extra commits but rather keep the package.json in-sync with releases that are created. Right now a release in github does trigger the workflow to create an npm package with that same version, just need a way to also update the package.json at the same time as well. Looks like there is some github actions that will handle this, and could work into the workflow when a release is created.