Ensure Correct SavedStateRegistryOwner Propagation in asComposableFactory

[ekeitho]

This PR enhances state management within asComposableFactory by ensuring that each view level correctly accesses its own SavedStateRegistryOwner, preventing premature or incorrect state restoration assumptions.

Problem

Previously, nested views in a hierarchy (e.g., grandparent, parent, and child views) could potentially retrieve a SavedStateRegistryOwner from a higher-level view (e.g., the grandparent) before intermediate levels (e.g., the parent) fully restored their state. This caused a state inconsistency where the child view could assume that all parent states were restored when, in fact, it wasn't. This caused a crash java.lang.IllegalStateException: You can consumeRestoredStateForKey only after super.onCreate of corresponding component.

Solution

To resolve this, this PR updates asComposableFactory by explicitly setting the SavedStateRegistryOwner for each view level through setViewTreeSavedStateRegistryOwner. This change ensures that each view accesses its appropriate state registry owner, maintaining accurate restoration tracking at each hierarchy level.