Separate release pipeline for support library and plugin

We are currently preparing release for both support library (NPM) and CLI plugin (PyPI) in the same pipeline as well as making a single tag for both. We should create separate release tags and entries containing its features and the packaged files. I would say the best way is to use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) and have the pipeline automatically create the change logs.

Start by locating the current release pipeline and the tagging and packaging steps for the NPM support library and PyPI CLI plugin. Define separate release tags and entries, each containing its features and packaged files, then determine how Conventional Commits can drive the generated changelogs. Done means the two release flows are independent and produce the expected artifacts and changelogs.

Written by the indexing model from the issue text.