Fix maven central release (#35)

* Fix documentation config

* Update dokka output

* Update website

* Add project name to pom

* Remove local changes from documentation

* Remove local changes from website

* Update dokka cleanup rule for new path

* remove dokka up-to-date checks

For some reason dokka is changing the styles.css file which means that CI can't verify if your remaining kdoc is up to date. Will investigate later.

Review @solcott's PR (#25)

* Update Kotlin to 1.4.21 and Coroutines to 1.4.2

Update other gradle plugins to latest versions except Dokka as it requires other updates to it's configuration
Update gradle to 6.7.1

* Replace externalEffectsChannel with SharedFlow

* Add test for external effect observer starting too late

* Downgrade gradle plugin version

To remain compatible with IntelliJ

* Apply PR feedback

Co-authored-by: Scott Olcott <scottolcott@gmail.com>

Prepare 1.0 release (#17)

Fix CI scripts (#12)

Add listeners functionality (#6)

Now you can observe which actions, mutations, or state updates are happening. Use with care as this might interfere with the MVI principles/benefits!

Workaround hardcoded/absolute paths being written by dokka plugin (#5)

Right now if I run dokka, the file documentation/mvflow/index-outline.html will contain many links (html anchor tags) to files in my own computer (href starting with /Users/me/myprojectfolder/...) which means this can't be shared in github/doesn't work when taken to other computers.

This PRs introduces a task that will look for those strings and remove them, making those links relative (and everything should still work).