Automate the publication of binary artifacts from CI

[labra]

The publication of artifacts could be automated from the continuous integration process to avoid manual errors.

One important aspect is to remove coverage code before publishing by activating coverageOff.

[thewillyhuman]

If we use automatic deployment for artifact publication we must add some kind of safe guard against no-test-passing code on Master. Else if non working code gets there can make fail any other project relying on this.

[labra]

Yes, I think we should publish only when all the tests pass and the version in file version.sbt changes.

Maybe sbt-dynver can help to keep the version updated, but I am not sure yet.

[labra]

I will try to automate this using sbt-github-actions, sbt-github-packages and sbt-ci-release