Semantic Release for CI-based npm publishing?

Instead of @tth always manually publishing new releases of @linguala/ui-components, we could use Gitlab-CI to do this chore.

Using semantic-release would be an option: https://github.com/semantic-release/semantic-release#how-does-it-work

Hint: This requires that people who push commits to master following a strict commit structure... (Workshop?) The CHANGELOG format might need to be adjusted as well.

• add semantic-release to devDependencies
• setup CI for npm publishing (add publisher account on npm)
• setup https://github.com/commitizen/cz-cli or https://github.com/conventional-changelog/commitlint to enforce commit messages follow a defined format #51
• publish first release with Gitlab-CI-runner