Improve release process

[mkobit]

Current process:

1. update version in build.gradle.kts
2. update release notes and version in changelog
3. update versioning information in readme
4. run local build, make sure HEAD up-to-date with remote master, no locally dirty files
5. run ./gradlew release (which locally git tags, git push, and uploads to gradle plugin portal)

this also assumes i have the proper local setup for the gradle plugin portal

I'd like to reduce some of this.
For example, maybe it just "tag and push" and let something like nebula.release perform the release process on Circle CI

[mkobit]

Seemed like I got this in a good place to only need to push a tag with x.x.x pattern, but not seeing workflow triggered - opened a forum post at https://discuss.circleci.com/t/tag-workflow-doesnt-work-despite-similar-setup-on-other-project-working/30514/2

[mkobit]

Going to manually release 0.9.0 since things with Circle aren't going as planned...

[mkobit]

Again have to manually publish after pushing

After setting up authentication to plugin portal

./gradlew final -P release.useLastTag=true --exclude-task test

Seems like something is busted on Circle CI side.

[mkobit]

Will look to simplify this in next release