Lifecycle KMP experimental support

[DevSrSouza]

Usage:

@Composable
fun MainView() {
    ProvideNavigatorLifecycleKMPSupport {
        Navigator(...)
    }
}

In the Screen, just use plain Lifecycle ViewModel Compose viewModel callback or any third party DI that already supports lifecycle kmp.

[versions]
androidxKmp-lifecycle = "2.8.0-rc03"
voyager = "next version"

[libraries]
voyager-lifecycleKmp = { module = "cafe.adriel.voyager:voyager-navigator", version.ref = "voyager" }
androidxKmp-lifecycle-viewmodelCompose = { module = "org.jetbrains.androidx.lifecycle:lifecycle-viewmodel-compose", version.ref = "androidxKmp-lifecycle" }

This PR also updates Compose KMP to 1.6.10

[rsicarelli]

Any particular reason for making it nullable and initialising it as null as well?

[DevSrSouza]

I have moved the default implementation to the Navigator module, when this is null, it will use the default implementation. The reason is for removing the android lifecycle API from the core module and move to the navigator, also avoid cycle dependencies

[rsicarelli]

maybe?

Suggested change

	namespace = "cafe.adriel.voyager.kodein"
	namespace = "cafe.adriel.voyager.lifecycle.kmp"

[DevSrSouza]

Nice catch! forget to replace

[rsicarelli]

I think this might lead to a warning like

A compileOnly dependency is used in the Kotlin/Native target 'ios....':

[DevSrSouza]

This is a old approach that I don't know if is still required. In the past, if you not add compileOnly to Compose KMP libraries, then, android only project would fail to use the library because it would not find the jetbrains android dependencies. I think this is fixed, but I not 100% sure without testing, for now, I will still keep this approach.

For the warning, we have a flag
https://github.com/adrielcafe/voyager/blob/main/gradle.properties#L12-L19

[rsicarelli]

any special reason why not saving it for onPause lifecycle as well?