Prepare for sbt-ci-release usage

[limansky]

Hi @lloydmeta ,

Finally, I've done some preparations for sbt-ci-release usage. I removed all version values, to make sbt-dynver work. This requires to set tag on the previous version properly.

Also it is needed to setup build variables, to make publish work. (see https://github.com/sbt/sbt-ci-release).

[codecov-commenter]

:warning: Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.71%. Comparing base (c76f948) to head (c53c5da).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #420   +/-   ##
=======================================
  Coverage   85.71%   85.71%           
=======================================
  Files          63       63           
  Lines         511      511           
  Branches       34       34           
=======================================
  Hits          438      438           
  Misses         73       73           

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[limansky]

To be honest, I haven't used sbt-ci-release myself too, but as I see it's a kind of meta-plugin for several things like sbt-sonatype, sbt-dynver, and sbt-gpg. I'm using sbt-sonatype and sbt-gpg in https://github.com/limansky/beanpuree, and some other projects.

1. As I see +publishLocal is still working, so you can use it to test without publishing to sonatype. (I've found what enumeratum-play/update task is broken when it called without cross-compile, but works fine as +enumeratum-play/update, I'm going to investigate it).
2. Yes, all the libraries will have the same version. So, once you set a tag for a new version CI task "publish" calls sbt task "ci-release" which internally calls a sequence of other tasks like +publishSigned and sonatypeBundleRelease.

[limansky]

I think you can also use show task to verify the sbt settings (show version, show publishTo, etc).