Migration to AndroidX architecture components

[arkivanov]

I have been thinking for a long time about completely migrating Decompose not only to androidx.Lifecycle (see #695), but also to SavedStateRegistry, ViewModel and the new NavigationEventDispatcher. For those who don't like the ViewModel API like me, it should be possible to create extensions based on AutoClosable from stdlib (like getOrCreateCloseable from Essenty). In a similar way, it should be possible to enhance the SavedStateRegistry API.

The idea is that GenericComponentContext will extend not only androidx LifecycleOwner, but also SavedStateRegistryOwner, ViewModelStoreOwner and NavigationEventDispatcherOwner.

Pros:

SavedStateRegistry seems to support passing a SerializersModule (of course, I could do the same in StateKeeper, but it's not straightforward). Also, in theory, it will also be easier to interop with the official navigation and other libraries. Easier adoption of Decompose.
And, well, it seems to be a standard already.

Cons: the mentioned AAC API is quite messy, as it's been carried over for a long time since Java times. There are plenty of opinionated APIs that I don't quite like to be exposed from Decompose.

Anyway, at this point I'm not even 100% sure that this is even possible to implement, I will need to try.

Add 👍 if you think this is a good idea, add 👎 if you don't like it.

[arkivanov]

Alternative options that I'm going to investigate is providing a separate module with extensions for SavedStateRegistry and ViewModelStore. So that we could have the best of the two worlds.

[arkivanov]

The new 3.4.0-alpha03 release adds JetpackComponentContext that exposes Jetpack Lifecycle, as well as ViewModelStoreOwner and SavedStateRegistryOwner. See the updated docs for more information.