Automate package release with Semantic versioning

[Ndpnt]

This PR allows to manually trigger the package release on GitHub and NPM with an appropriate version bump and distribution tag.

Changelog file (based on Keep a Changelog) should be partially maintained manually by adding changes in the appropriate subsection type (Added, Changed, Deprecated, Removed, Fixed, Security) in the Unreleased section. Then the release workflow will automatically generate the proper entry in the changelog and will clean the unreleased section.

To trigger the release :

• go to the Actions tab
• select the Release workflow
• click on the Run workflow dropdown
• select the Release type
• then click on the Run workflow button

Heavily inspired from Superface.ai release process

[Ndpnt]

Note: the release workflow will be available on the Actions tab only when this PR is merged on the main branch.

[martinratinaud]

I approved but could not test of course.

When this is done, we should update all instances with the npm version

[MattiSG]

As seen in a synchronous call with @ndpnt, we want to:

• Make deployment automated and continuous.
• Use Common Changelog instead of Keep a Changelog.
• Document this in the CONTRIBUTING.
• Obtain version number bump from a tag in the title: ## Unreleased [patch] [minor] [major].
  • This will enable learning. Over time, when we have consistent interpretation, we might automate that from other signals from the Changelog.
• Remove dist-tags management since they are irrelevant in a CD context.

[MattiSG]

I don't find it relevant to downgrade the version to 0.0.0. This will lead to multiple versions in the VCS having the same version number. I don't think it's a problem if the first published version is 0.16.0 🙂

[MattiSG]

We want to publish on NPM under the name opentermsarchive.

[MattiSG]

I expect a conflict will happen on the v0.17.0 tag that has already been added to the repo, it should probably be removed before merging 🙂

[Ndpnt]

I expect a conflict will happen on the v0.17.0 tag that has already been added to the repo, it should probably be removed before merging 🙂

Already removed ;)