Android13 changes

[ghost]

• new google API to handle in-app language changes
• simple backup configuration
• new savedstatehandle to get/set StateFlow's from it
• ability to test changes with fragments
• ability to pick 1/multiple images from gallery
• 2 helper methods to observe changes, made by other fragments, and to get savedhandle to make this changes
• use hiltViewModel() method instead of "by viewModels" helper method in compose fragment

[Skyyo]

1. pushed few changes since new google API to handle in-app language changes was misused. Though there is an issue on Android versions lower than Android 13 - activity isn't restarted automatically. Not sure if that's intended, or will be changed when Android 13 is released. If this issue persists - we will need to add a TODO into the readme here and to check on it later
2. ability to test changes with fragments - can you please elaborate on this one? Didn't understand what to check.
3. 2 helper methods to observe changes, made by other fragments, and to get savedhandle to make this changes - let's please try to apply them in the package named navigateWithResult, if it simplifies things.
4. use hiltViewModel() method instead of "by viewModels" helper method in compose fragment - can you please remind me if we can drop dependency or is there any noticable benefit of doing so? Seems it makes more sense to use the current approach until we ditch Fragments completely

Good job overall @ahamula !

[ghost]

1. Activity do restarts, but it restores previous state afterwards. Please, add logs in onCreate method to verify it. I don't know if other projects have same requirements as Puff, but on Puff there is requirement to turn hebrew as default locale, so we need to use activity instead of fragment/composable, because language screen not necessary will be on top. On Puff there is some guidance screen on top, and so we can't apply default language logic in fragment.
2. There was flag USE_BOTTOM_NAVIGATION_WITH_FRAGMENTS in MainActivity, that you was able to switch on/off to verify that language change work with fragments fine. Also we were able to test some other features with fragments, not fully composable's screens just to turn on this flag.
3. I'm talking about these 2 methods: fun NavigationDispatcher.observeBackStackStateHandle() and fun NavigationDispatcher.observeNavigationResult() in NavControllerExtensions, not clear where you'd like them to put.
4. We can drop "by viewModels" extension, and instead use hiltViewModel() method inside composable. Not much noticeable benefits, just we can remove one method, and don't have long "non-composable" methods (I mean onCreateView will become in 4-5 lines long). You can check code of some fragment from application.fragment package. So, no much benefit, but we can simplify migration from fragment to composable in future (if it'll happen :) ) Because it's all copy paste, only "main composable" part differs between fragments

@Skyyo

[Skyyo]

1 - in case activity restarts, we need to ensure that everything else knows that locale changed. We want every Android version to react immediately, like on the Android 13 atm.
2 - no need or fragments in this project. Didn't delete them yet, since there is still usage of your 2 extensions.
3 - here. These screens showcase passing fields up & down
4 - got it, won't be using it for now.

[ghost]

@Skyyo Fixed navigation in "dog"/"cat" places, fixed layout direction on android 12