Migrate to kotlinx-io

[xxfast]

Builds on top of @mani1232's #112

• Update deps and migrate from okio to kotlinx.io
• Update example
• Support for other formats (Will be added in the future)
• Ignore kotlin metadata
• Bump yarn lock for kotlin 2.0
• Fix kstore file tests
• Bump api
• Prepare for snapshot 0.9.0
• Fix kover code coverage reports
• Fix github action for kover coverage report
• Downgrade to kotlin 2.0.10
• Remove kstore formats
• Add factory method for custom codecs
• Update documentation

[github-actions]

Code Coverage

File	Coverage [87.10%]	✅
kstore-file/src/commonMain/kotlin/io/github/xxfast/kstore/file/FileCodec.kt	78.57%	❌
kstore-file/src/commonMain/kotlin/io/github/xxfast/kstore/file/KStore.kt	76.92%	❌
kstore-file/src/commonMain/kotlin/io/github/xxfast/kstore/file/extensions/KListStore.kt	83.33%	✅
kstore-file/src/commonMain/kotlin/io/github/xxfast/kstore/file/extensions/KVersionedStore.kt	96.55%	✅

Total Project Coverage	92.16%	✅

[xxfast]

Hi @mani1232 & @8cAyqpVKio

I've added a new overloaded factory method that lets you provide a custom codec (if you want your custom file format) so this should theoretically let you use a format other than JSON)

Again, this is out of scope for now but should unblock anyone who wants to use other unstable serialiser formats

[mani1232]

I have a couple questions:
Does it make sense to save not immediately, but every X minutes?

And will it be possible to set your own compression algorithm

[xxfast]

Do you mean to schedule the writes to the disk?

KStore API for writes/reads all suspended so that it will block whichever coroutine it is invoked from. This is by design.

There's couple advantages for this approach

• This lets the call-site handle exceptions inline. This wouldn't be possible with exceptions thrown from scheduled tasks
• This approach preserves the write-order. (as demonstrated in this unit test)

However, any asynchronous behaviour can still be implemented on top of this - with coroutines.