Bonus: GH Actions - release automation

[marcanpilami]

After #20 all Docker user needs are served but not classic deployment users - they need to download a package on the release page.
So extend the pipeline to create a release (named after the tag) and include a tar.gz of the "ready to run with sqlite" directory from the docker image without any modifications.

Release must stay draft.

[abessette]

extend the pipeline to create a release

On which event, action... should the "create release" triggered ?

Regarding the fact that we listen to the release event on the previous issue #20, we might want to stop listening on release event and create it on every tag on the master branch or specific tag pattern.
"Or" update the release with the tar.gz file...

[marcanpilami]

Remaining: issue with release update inside GH.