Revert "Update ambient indication container"

Revert submission 16336967-beverlyt_center_ambient_indiciation_text

Bug: 206122454
Reason for revert: b/208330808
Reverted Changes:
I176eec0cc:Update ambient indication container
I85d7684aa:Update the ambient indication container

Change-Id: Ie75d9338d2933e32a920ada2cf85d450375233b5

- Move the ambient indication container to the keyguard
bottom area so that the KeyguardBottomAreaView can control
the x and y burn-in offsets so that they are equivalent to the
charging text burn in offsets.

Test: atest KeyguardBottomAreaTest
Test: manual
Bug: 206122454
Change-Id: I85d7684aa7f229a5c04a6c35ea0cffa449b876e4

- The disable() call on the binder thread can race with this call on
  the main thread due to this 1) fetching the old values on the main
  thread, then 2) trying to synchronize on mLock by calling disable()
  (which the binder thread is currently holding) and then 3) applying
  the previous flags immediately after the fresh disable flags are set
  by the binder call.

Bug: 205921118
Test: atest SystemUITests
Change-Id: I5dd4d2d248b6c1ab6d1677e2bb915100cd3e4f4e

Also, use SystemUI dialog theme.

Test: manual
Test: atest DndTileTest
Fixes: 206454318
Fixes: 206730944
Change-Id: I599935e28ab6d6f6ad1fa497f4eeea652b74dad6

* Added logic into already existing class used
for A11y, renamed that to NavbarHelper
* Prevent destory() in TaskbarDelegate from being called
without init() call first

Bug: 204273914
Test: Assistant is invokable on launcher unfolded
in gesture nav

Change-Id: Ic3232f375c68fd444c7378bc8ddd5a9b6991bd69

* Show the bouncer after 3 consecutive UDFPS failures
* Show the bouncer if the shade is expanded and UDFPS is in lockout
due to too many attempts
* Make sure to show the lockout reason bouncer prompt if there
have been too many attempts

Test: atest BiometricsUnlockControllerTest UdfpsKeyguardViewControllerTest StatusBarKeyguardViewManagerTest
Test: manual
Bug: 206996872
Change-Id: I9992acd121de5b422801228777e833043764379a

Margin and padding calculation should actually be part of the layout
pass, such as it cannot be out of sync.

Test: pull down QS with Media on LS, split shade, launcher
Test: atest QSSquishinessControllerTest
Fixes: 204517562
Change-Id: I0001502f7c3368060e7b8fc93c753b05a8386aa6

Test: atest KeystoreTests
Bug: 196118021

Merged-In: Ic6e60752faa986debe3d325f54242cffaa03b336
Change-Id: Ic6e60752faa986debe3d325f54242cffaa03b336

This fixes the contract between equals and hashCode in
AndroidKeystoreKey and AndroidKeystorePublicKey.

Bug: 196118021
Test: See next CL.
Merged-In: I3f7e6d72d53c7051c13daeb5aa6ce1abf4eb0cc5
Change-Id: I3f7e6d72d53c7051c13daeb5aa6ce1abf4eb0cc5

In addition, add a ripple effect to the button.

Fix: 198347324
Test: N/A
Change-Id: Ibd33f32cf4908ae9d3d02d8043e625e24123aff7

In split shade the NSSL is no longer full screen, so the assumption that getX was the absolute X coordinate of the touch was wrong; as a result the NSSL dismissed the guts because it thought the touch was somewhere in the NSSL but not in the guts view (or any other view).

Fixes: 204283146
Test: manual
Change-Id: I634d378e162e20ed277b164a506d7dace56c8525

Fix: 203817448
Test: manual
Change-Id: Icc339dd7a87284af31abe70fff9ede2868f5add9

1. Check Task#effectiveUid instead of rootActivity Uid for TF creation
2. Pass in the caller uid/pid for activity starter instead of using
   Binder.getCallingUid() after clearCallingIdentity()

Bug: 205996115
Test: atest WmTests:TaskFragmentOrganizerControllerTest
Change-Id: I1b1470a95d55820dd6d69658c570c3e5640ebe55

- Now that split bounds info is tied to the recent tasks provided to
  Launcher, we need to notify of the changes when the info changes

Bug: 206868465
Test: atest WMShellUnitTests
Test: Split app pair, go to overview, go back to app, change divider
      position, then go back to overview -> ensure pair is drawn
      correctly
Change-Id: Id7926a20ab3be3a9cb5eb832fb321c80bd60bae0

When pip app could show when locked(e.g. Maps) and user click
expand to split button, the keyguard occluded callback usually
come before onStageVisibilityChanged then cause split exit by
keyguard occluded

Fix it by add more condition check, we should do it only when
device waking up, keyguard occluded and only the stage included
show when locked app is visible then exit split to show that app
full screen.

Bug: 202740657
Fix: 204527184
Test: manual
Test: pass existing tests
Change-Id: Id63e8dee42337b5dd4f767a866a965cb97761cf0

Or the organizer could start activity or perform unnecessary
actions while in background.

Bug: 204385547
Test: atest TaskFragmentOrganizerControllerTest
Change-Id: I6aa731293d34cd481841a0af2d339a659a148b2e