Packaging of the tool

[MokhFn]

Hi,

While working on #120 for the project, i opted for using zet.releaser command fullrelease. When merging a PR, this command will :

• Update the changelog automatically (assuming you filled it)
• Create a new Tag
• Create a python package and upload it to PyPI

I implemented this withing tox environments.

The question is, if this was okay with the team ?
If so, the core maintainers should create a new Repository (and maybe even Organization) on PyPI for this project, name it, then create a token to be able to auth, when uploading packages.
This token needs to be added as a secret within Github, and i'll need the name of the secret (for example, i called it PYPI_TOKEN), that way i can use it from Actions securely.

I did a small release test that you can find here.

Thanks in advance, and please keep in mind that i remain open to any suggestions.
PS : The release test is only to confirm the gh actions perform as expected, the software won't work.

@dimkarakostas @LadyChristina @mtefagh

[dimkarakostas]

The tool is still in heavy development, so I'd rather wait until it is in a more stable setting before packaging.

[MokhFn]

Okay, i'll keep #120 and the related PR open untill further instructions.
I will add a manual changelog in the meanwhile if you think that could be helpful.
Please let me know when packaging becomes "of use".