fix(Android, Stack): Fix FormSheet - SafeAreaView integration (#3336)

## Description

Bugfixing the integration between SafeAreaView and FormSheet. I'm
preventing the consumption of the bottom inset, allowing it to be passed
to SAV component. Additionally, I'm adding some other fixes I caught
during testing, for fitToContents and zeroing the bottom inset for
keyboard handling.

> [!WARNING]  
> Note:
> We do not manipulate the top inset manually. Therefore, if
`SafeAreaView` has top insets enabled, we must retain the top inset even
if the formSheet does not currently overflow into the status bar.
>
> This is important because in some specific edge cases - for example,
when the keyboard slides in - the formSheet might overlap the status
bar. If we ignored the top inset and it suddenly became necessary, it
would result in a noticeable visual content jump. To ensure consistency
and avoid layout shifts, we always include the top inset upfront, which
can be disabled from the application perspective.

Creating a follow-up ticket for handling some cases that I wasn't able
to cover with SAV:
software-mansion/react-native-screens-labs#565

Fixes:
software-mansion/react-native-screens-labs#457
, #2896

## Changes

- Updated the logic for consuming insets in the `SheetDelegate`
- Added a new example for testing.

## Screenshots / GIFs

Here you can add screenshots / GIFs documenting your change.

You can add before / after section if you're changing some behavior.

### Before


https://github.com/user-attachments/assets/c32fc9f4-63e3-41b2-ab31-110a3ec46d68

### After


https://github.com/user-attachments/assets/647c1674-535e-4dd8-8156-9b490588d123

## Test code and steps to reproduce

Added `Test3336` for testing.

## Checklist

- [x] Included code example that can be used to test this change
- [x] Ensured that CI passes

Author: t0maboro

android/src/main/java/com/swmansion/rnscreens/Screen.kt

@@ -142,6 +142,9 @@ class Screen(
         if (usesFormSheetPresentation()) {
             if (isSheetFitToContents()) {
                 sheetBehavior?.useSingleDetent(height)
+                // During the initial call in `onCreateView`, insets are not yet available,
+                // so we need to request an additional layout pass later to account for them.
+                requestLayout()
             }
 
             if (!BuildConfig.IS_NEW_ARCHITECTURE_ENABLED) {

android/src/main/java/com/swmansion/rnscreens/bottomsheet/SheetDelegate.kt

@@ -311,26 +311,14 @@ class SheetDelegate(
     ): WindowInsetsCompat {
         val isImeVisible = insets.isVisible(WindowInsetsCompat.Type.ime())
         val imeInset = insets.getInsets(WindowInsetsCompat.Type.ime())
+        val prevSystemBarsInsets = insets.getInsets(WindowInsetsCompat.Type.systemBars())
 
         if (isImeVisible) {
             isKeyboardVisible = true
             keyboardState = KeyboardVisible(imeInset.bottom)
             sheetBehavior?.let {
                 this.configureBottomSheetBehaviour(it, keyboardState)
             }
-
-            val prevInsets = insets.getInsets(WindowInsetsCompat.Type.navigationBars())
-            return WindowInsetsCompat
-                .Builder(insets)
-                .setInsets(
-                    WindowInsetsCompat.Type.navigationBars(),
-                    Insets.of(
-                        prevInsets.left,
-                        prevInsets.top,
-                        prevInsets.right,
-                        0,
-                    ),
-                ).build()
         } else {
             sheetBehavior?.let {
                 if (isKeyboardVisible) {
@@ -344,12 +332,19 @@ class SheetDelegate(
             isKeyboardVisible = false
         }
 
-        val prevInsets = insets.getInsets(WindowInsetsCompat.Type.navigationBars())
+        val newBottomInset = if (!isImeVisible) prevSystemBarsInsets.bottom else 0
+
+        // Note: We do not manipulate the top inset manually. Therefore, if SafeAreaView has top insets enabled,
+        // we must retain the top inset even if the formSheet does not currently overflow into the status bar.
+        // This is important because in some specific edge cases - for example, when the keyboard slides in -
+        // the formSheet might overlap the status bar. If we ignored the top inset and it suddenly became necessary,
+        // it would result in a noticeable visual content jump. To ensure consistency and avoid layout shifts,
+        // we always include the top inset upfront, which can be disabled from the application perspective.
         return WindowInsetsCompat
             .Builder(insets)
             .setInsets(
-                WindowInsetsCompat.Type.navigationBars(),
-                Insets.of(prevInsets.left, prevInsets.top, prevInsets.right, 0),
+                WindowInsetsCompat.Type.systemBars(),
+                Insets.of(prevSystemBarsInsets.left, prevSystemBarsInsets.top, prevSystemBarsInsets.right, newBottomInset),
             ).build()
     }