ViewBehavior will be a static inner class for InputDevice, providing
View-related behaviors pertaining to an InputDevice. We have added an
API in InputDevice to return its ViewBehavior.

This will be helpful if different InputDevice properties affect the way
an input- generated MotionEvent should be handled by a View. For
example, we have implemented a "shouldSmoothScroll" API in this change.
This API is to tell Views processing motions generated by the
InputDevice to prefer animating scrolls caused by such motions, to
deliver a better quality scrolling UX than compared to a regular scroll
that jumps by X pixels in a single frame.

Note that, a single ViewBehavior instance contains all behaviors for a
single InputDevice. This is unlike the other inner static class of
InputDevice: MotionRange. This decision of making a single ViewBehavior
contain all behaviors is made because not all View behaviors may depend
on source+axis (e.g. there could be a behavior that is globally
applicable to the whole InputDevice).

Bug: 246946631
Test: unit tests, manual
Change-Id: I65cf7d6556e26d199c9021f53bdae183f21d3c6d

Merge "Do not pass assist data and screenshot to VIS if one of the windows is from private profile" into main

Extend the shaderlib to support common loading effects.

Bug: 282007590
Test: m
Flag: ACONFIG shaderlib_loading_effect_refactor DISABLED
Change-Id: I33f3044de5cefbbe2c4026101f6c4ad6a0b7642d

This reverts commit 248336b7.

Reason for revert: Made a test flaky: b/323237500

Change-Id: Id301e18ddf4b126c5bf09ac4311482b288af9117

Some tests rely on reporting failures from another thread; upstream
JUnit quietly eats these exceptions, which can result in misleading
"pass" signals when migrating existing tests.  To match the behavior
of a physical Android device, we now monitor for uncaught exceptions
and report them as test failures.

Some tests are relying on `ActivityManager` static methods, so offer
those on Ravenwood.  Leaves "current user" as `USER_SYSTEM` for the
moment, but we'll likely think more about how to customize it as
part of bringing a real `ActivityManager` online.

Some tests rely on `VibrationAttributes` which is a basic holder
object, so offer it on Ravenwood.

Tests to verify all of above.

Bug: 319647875
Test: atest SystemUiRoboTests
Test: atest SystemUiRavenTests
Change-Id: I1bc5bbc7b4eadf1c6d19c0044012a945ce377a20

Check if there is any window on the current display is coming from
the private profile, if so, do not allow passing the data to VIS.

Bug: 323128958

Test: Added tests in android.voiceinteraction.cts.VoiceInteractionServiceTest
Test: Manual. Write a simple VIS app for testing.
1. Trigger the VIS test app when the personal app is in foreground.
The VIS app can get the data.

2. Trigger the VIS test app when the private space app is in foreground.
The VIS app cannot get the data.

3. Enables split screen. One app from personal and one app from private
space. The VIS cannot get the data.

Change-Id: Ic0490ff8da6fd74ab8c762fee13e1822abdf8acd

Bug: 304574518
Flag: ACONFIG window_surfaces.screen_recording_callbacks DISABLED
Test: ScreenRecordingCallbackTests
Change-Id: I76ae2035d65989f17b620b16ae457e8fdd65cb9e

* changes:
  Add WRITE_VERIFICATION_STATE_E2EE_CONTACT_KEYS to Shell.
  Add APIs for apps to update Contact keys of other apps.
  Add WRITE_VERIFICATION_STATE_E2EE_CONTACT_KEYS permission.