Automate package release with Semantic versioning

[Ndpnt]

This PR trigger a package release on GitHub and NPM with an appropriate version bump when merged on the main branch.

Changelog file is based on Common Changelog.

[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 ;)