CI: Automate release workflow

[Finii]

[why] Releasing is too hard.

[how] The maintainer needs to set a new version in the package.json. Afterwards the release draft creator can be manually triggered on the Actions tab of the Github repo.

This will draft a release with a new font generated from the current vectors. And the current commit will be git tagged with the release version.

Fixes: #29

[Finii]

I imitated the contents of the release v1.0.1 files. Not sure that all that files are really useful. Otoh do not know if this npm thing need it.

[Finii]

Just noticed that the files are not automagically compressed. I'm always confused, sometimes they are, sometimes not. I think the normal action artifacts are always packed, and the release artifacts not... :thinking: :grimacing:

[Finii]

Ok, this seems ready. I tested everything except the final publish-to-npm.

Will try to use the workflow to get v1.0.1 published, this will involve some tricks, though.

[Finii]

Test on v1.0.1, success:

[Finii]

https://www.npmjs.com/package/font-logos

[Finii]

Actual assets missing?? Working on it...

[Finii]

Fixed via the following commits. Needed to increase version because NPM does not allow any other change

• 881cc5e Rerelase fixed NPM package, no change
• 8d6d767 CI: Fix missing assets in npm

Sorry :unamused: