Set up a common workflow to push a package to npm when we issue a release

### Prerequisites

- [X] I have written a descriptive issue title
- [X] I have searched existing issues to ensure the feature has not already been requested

### 🚀 Feature Proposal

Why?

To release a new version of any package, we lose a somewhat significant amount of time (checking out locally, syncing, etc.)

An example of how simple things can be: https://github.com/gurgunday/html/blob/e60791ff5f557c9eb51c75f8f80008e74bfa3ced/.github/workflows/npm-publish.yml

And the action runs automatically after a release is issued:
https://github.com/gurgunday/html/releases/tag/v7.0.0
https://github.com/gurgunday/html/actions/runs/6941110154

We just need to create an automation token on NPM and add it to GitHub

Another benefit: it also **[signs the commit](https://docs.npmjs.com/generating-provenance-statements)** during the workflow, so if we have any paranoid users, they can verify that the release matches to what they see on GitHub

What do you all think?

### Motivation

_No response_

### Example

_No response_