[ViewPager2] WindowInsetsApplier break insets with BottomNavigationView below API 30

Nobody has claimed this yet.

**Description:** WindowInsetsApplier break insets with BottomNavigationView below API 30.

**Expected behavior:** WindowInsetsApplier will not break insets with BottomNavigationView.

**Source code:**
on activity :
```
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
binding = ActivityMainBinding.inflate(layoutInflater)
setContentView(binding.root)
WindowCompat.setDecorFitsSystemWindows(window,false)
// fix the broken `WindowInsets` dispatch of old API versions (< 30)
WindowInsetsApplier.install(binding.viewpager)
binding.viewpager.isUserInputEnabled = false
bottomNavigationMediator =
BottomNavigationViewMediator(binding.bottomNavView, binding.viewpager)
bottomNavigationMediator.attach()
}
```

on layout:
```

```

Above codes will reproduce the issue below API 30.

Once we switch the order of ViewPager2 and BottomNavigationView in xml, the issue is gone:
```

```

But with version 1.0.0 of ViewPager2 , or not calling `WindowInsetsApplier.install`, no matter order is with ViewPager2 and BottomNavigationView, this issue will not happen.

**Minimal sample app repro:**
[ViewPager2Issue](https://github.com/kolyneh/ViewPager2Issue)

**Android API version:** Android API 28

**Material Library version:** material 1.9.0 and viewpager2 1.1.0-beta02

**Device:** AVD API 28

Start with the linked ViewPager2Issue sample app and the WindowInsetsApplier.install(binding.viewpager) call. Reproduce on API 28 with ViewPager2 before BottomNavigationView, then compare the reversed XML order and the behavior without installation. Done means insets remain correct with the original layout order below API 30.

Written by the indexing model from the issue text.