* changes:
  Support back to split
  Support back gesture to split pair in background

This change allows notifications with full screen intents to show that FSI on a ranking update if they meet specific criteria (previously suppressed only by DND; not older than a few seconds; now no longer suppressed).

FSI on update only happens when the flag FSI_ON_DND_UPDATE is set to true.

Bug: 248325248
Test: HeadsUpCoordinatorTest, manual verifying the FSI actually shows up on update

Change-Id: I810ae951bc96908cc66a8831f88730021bdb64b6

Also renames the method and adds doc. There were 3 calls to
touchXOutsideOfQs and two of the usages were also checking whether
split shade was enabled. Adding the split shade check to the third
fixed b/259591763. Since all usages are paired with the split shade
check, I've moved that into the method and renamed it accordingly.

Fixes: 259591763
Test: manual and atest
Change-Id: I01edaeceac0a04cc1d2d9af22fbdaf88d3a3162f

Bug: 260861673
Test: manual.
Change-Id: I2382dea27a6405f77ab0b5b0cec19ae449245630

Handle split screen enter while it still running background case.

Bug: 236317871
Fix: 235515745
Test: manual
Test: pass existing tests
Change-Id: Id75611afc446f74864e016cbaa51e501dcd55612

Split screen will be dismissed right after both sides of the split
were occluded. So if users try to use a back-gesture to go back to
the previous split pair, it’ll be back to home instead of going
back to the split pair. This CL support the split pair in background
to make split experience better.

Bug: 236317871
Test: atest com.android.wm.shell.SplitLayoutTests
Change-Id: I1ead65011ced82e1faa24ccfbc8bf474828fc7dc

[automerger skipped] Merge "DO NOT MERGE:Deflaky testLoggingStats_search_success" into sc-dev am: d530cd1a am: 393f374f -s ours am: 7ba46d7f -s ours am: 7b6b4fec -s ours am: b61a643b -s ours

am skip reason: subject contains skip directive

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20621276



Change-Id: I240693d1461dae969f05681c8dd74e21bcd88f0d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

[automerger skipped] Merge "DO NOT MERGE:Deflaky testLoggingStats_search_success" into sc-dev am: d530cd1a am: 393f374f -s ours am: 7ba46d7f -s ours am: 7b6b4fec -s ours

am skip reason: subject contains skip directive

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20621276



Change-Id: Iae35f9a5363cdf14d37b72e1d01ea52f87a734a0
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

This crash is caused by doble tap sometimes trigger onResizing at
same time. This might be gesture limitation. We should avoid doing
screenshot fade-out animation at such situation because its bounds
didn't change.

Fix: 261809537
Test: manual
Test: pass existing tests
Change-Id: Ida6b6e5f9a19cc2a403bb97d8bc1744c24ad90f7

* changes:
  Revert "Create controller for desktop prototype 2"
  Revert "Implement showDesktopApps"
  Revert "Implement move to desktop and fullscreen"

Merge changes from topic "presubmit-am-8134571e02a14812820dc4626241cf6f" into sc-qpr1-dev am: ba36fd90 am: 74dd009a am: bacaccab am: 8de00c63

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20621276



Change-Id: I65c2f624841397aa61cf7b5cd8578c596a0cbd0b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

[automerger skipped] [automerge] DO NOT MERGE:Deflaky testLoggingStats_search_success 2p: 2c01a0bb am: a85abd57 -s ours am: 7f3dd285 -s ours am: 9d903936 -s ours am: 6d85caa4 -s ours

am skip reason: subject contains skip directive

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20621276



Change-Id: Ie934ef6bdd5ca78c6c664721b2db6480d12121c2
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>