Publication workflow became incompatible with our versioning scheme

[Fabilin]

Recent versions of the np package disallow setting a specific release version, which breaks traditional use of the manual workflow (related issue: sindresorhus/np#748).

Since our versioning scheme is not truly semantic-based (major representing the year, and minor being either March or September), we cannot use the built-in update keywords either.

Solutions

The solution could be one of the following:

• Change our versioning scheme (major change, out of line with the rest of the TOCK ecosystem)
• Downgrade the np package to the last known working version (8.0.4)
• Remove the np dependency and rely on regular yarn publish

Considering the np package is not intended to be used in CI in the first place, I believe the right move is to cut it from the workflow. It should also be noted that the prerelease preset bumped only the patch version component, which was usually inadequate considering we most often make prereleases for major versions.