This is effectively a follow-up to b/180881870

The fix to that bug (https://android-review.googlesource.com/1783607) stored the window parameter from one of the constructors to Impl30.

However, this was not the primary constructor, which means that only instances of WindowInsetsControllerCompat constructed with a Window will be able to workaround b/180881870 on API 30.

In particular, the code-path that uses WindowInsetsControllerCompat.toWindowInsetsControllerCompat(insetsController: InsetsController) bypasses the window constructor, meaning that the bug will still occur on API 30 with any method of retrieving the WindowInsetsControllerCompat with that code-path.

Those methods include:

ViewCompat.getWindowInsetsController(view: View)
WindowCompat.getInsetsController(window: Window, view: View)
WindowInsetsControllerCompat.toWindowInsetsControllerCompat(insetsController: InsetsController)

The current workaround is to avoid all of the above methods, and instead directly use the proper constructor: WindowInsetsControllerCompat(window: Window, view: View).

As a proposed fix, the constructor of WindowInsetsControllerCompat that doesn't take a Window should be deprecated for API 30, since the Window is required to workaround b/180881870. This would necessarily bubble up to the other methods, ensuring that the bug will be fixed across all versions.