Automate publishing of new versions

[karlhorky]

Prerequisite: #177

Publish new commits of eslint-config-upleveled in main that pass the tests automatically to npm.

For the version numbers, we may want to introduce some kind of commit message format like Conventional Commits. Should do some research here to determine what the best, least disruptive thing is.

We should probably also use the new npm Granular Access Tokens, including the IP ranges:

npm has supported automation tokens for quite some time. Automation tokens allow you to publish to any packages that the owner of the token has permission to. Until now, it was not possible to create tokens with a least privilege model—to limit the impact of an accidental or deliberate misuse of the token. The new granular access tokens will allow you to do exactly this. You can now create tokens that can publish only to a limited set of packages and/or scopes.

Granular access tokens also let you limit npm API access based on allowed IP ranges and come with an expiration period of up to one year.

• https://github.blog/2022-12-06-new-npm-features-for-secure-publishing-and-safe-consumption/#granular-access-tokens-help-publishers-create-tokens-with-limited-access
• https://docs.npmjs.com/about-access-tokens#about-granular-access-tokens

Similar to upleveled/preflight#342