Document release process better for pushing changes to NPM

[mrchrisadams]

Right now, we use the tool np to automate some of the steps for publishing code to npm.

I don't think I fully understand how the version numbers are updated in the source code compared to on npm, and it has lead to a few confused releases of new code to npm, like with a recent shortlived push of what would have been a patch release
taking us to 0.11.1 causing a deploy of 0.10.5.

This issue is to document our release process better, and if necessary check with folks who deploy npm packages more frequently than us using np, so we have a predictable and drama-free way to release code.

Stuff to cover:

• how to publish a patch release
• how to publish a minor release
• what to do if make a mistake (i.e. understanding the unpublishing process)

[fershad]

@mrchrisadams we've got this now published in our Readme, as well as details about where releases will be communicated as well. Okay for this issue to be closed?

https://github.com/thegreenwebfoundation/co2.js?tab=readme-ov-file#publishing-to-npm