fix: null-check widgetFragment before cast

See merge request e/os/BlissLauncher3!87

Fix emulator crash

See merge request e/os/BlissLauncher3!89

- In case view is not ready, fragment yielded may be null

fix: Ensure dock bounds are aligned on phone

See merge request e/os/BlissLauncher3!86

- This is only needed on tablet to prevent clipping of
  notification badges with more dock icons

fix!: Ensure at or above window insets on minus-one

See merge request e/os/BlissLauncher3!84

fix: Update click receivers for two-pane widget picker as well

See merge request e/os/BlissLauncher3!82

fix: Properly pick width for app suggestions

See merge request e/os/BlissLauncher3!80

fix: Resolve determination of next empty space in landscape

See merge request e/os/BlissLauncher3!78

- Landscape uses transpose wherein the rows and columns are
  switched. We need to use the fixed vars to properly determine
  a valid position. This is then taken over by CellPosMapper

BlissLauncher3: Rebase v1-u-tablet onto v1-u

See merge request e/os/BlissLauncher3!76

BL3: Rebase tablet changes for v1-u

See merge request e/os/BlissLauncher3!74

- Fixes widgets not laid out on mobile

- Calling createBitmap with just width and height completely disregards the
  density of input bitmap.
- We can just copy input bitmap and overwrite that to save us the trouble

- As per mockups here:
  https://gitlab.e.foundation/e/os/backlog/-/issues/2395#mock-ups

- Often when rotating, translation of the wrong dimension is used
- This happens because the view draws before a new rotation is committed,
  causing DisplayController to report old dimensions
- Also readjust translation onConfigChanged/rotate

- Also spotless amends

- When launcher is in foreground, especially with taskbar, it may
  stall/lock the UI thread.
- If the model is in the middle of loading and hasn't ever finished
  loading, it may need the user to navigate to another app or lock the
  device to finish model load, which is terrible UX
- This has worked so far but is a noticeable issue on tablets, and slower
  phones too
- Do not wait for idle and continue scheduling work on the UI thread so
  that the model has fully loaded at least once. After this, it can stall
  all it wants

- WidgetFullSheet may try to remove "ghost" widgets
- It assumes the list is mutable and calls removeIf. To prevent a crash
  initialize with ArrayList instead of List.of()

- Also test on phone to verify that the changes do not affect isPhone UX