fix(Android): status bar insets for formSheet

[kligarski]

Description

Status bar insets were not handled properly when opening the formSheet with initial height that was greater than safe content area. The bug is directly connected with how BottomSheetBehavior works. For unknown reasons, onChildLayout sometimes isn't called after BottomSheetBehavior's insets handler runs. In this PR, we override Screen's setOnApplyWindowInsetsListener (used by BottomSheetBehavior to register its handler), to make sure to request the layout after the listener runs.

The problem

On first layout, BottomSheetBehavior registers the inset listener which updates insetsTop field. In onLayoutChild, BottomSheetBehavior uses insetsTop value to calculate childHeight which is then used to calculate fitToContentsOffset. fitToContentsOffset is returned from getExpandedOffset() if isFitToContents == true (which is the case for single and two detents in screens). If isFitToContents == false (i.e. we use 3 detents), getExpandedOffset() uses insetsTop directly. When layout wasn't called after the insets handler, previous value was used which caused the sheet to go under the status bar.

Fixes #2896.

Changes

• add custom setter for onApplyWindowInsetsListener
• add Test2896 test screen (unable to create e2e test because content behind formSheet still has visibility = VISIBLE)

Screenshots / GIFs

Before	After
before_2896_fix.mp4	after_2896_fix.mp4

Test code and steps to reproduce

Run example app and open Test2896 test screen.

Checklist

• Included code example that can be used to test this change
• Ensured that CI passes

[kkafar]

Beside my wrong suggestion to use ArraySet last time, this one looks good!

[kkafar]

I have follow up question that just popped in my head

[ilteoood]

Any chance that we get this PR released soon?

[t0maboro]

The work is continued here: #3336