Fix our Release Action (or remove it)

[jeanmarc]

There is an old release action that gets triggered on pushes to develop (direct commits or PRs). It uses old secrets (they have not yet been updated), and probably interferes with the current setup where we manually release (tag, sbt publishSigned, sbt sonaUpload).

The sbt-ci-release picks a version based on the HEAD of develop and the distance to the latest tag, which means it typically does a SNAPSHOT release of that latest tag.
This means, if we manually released v0.5.0, and then push something to develop, the ci release will publish 0.5.0-SNAPSHOT. I think it should actually produce 0.5.1-SNAPSHOT releases (the patch+1 version of the latest release).