Track lockout end times in LockSettingsService

Fix the issue where lock timeouts triggered in one process
are not known about by other processes until after the first
guess is made. After this fix, getLockoutAttemptDeadline returns
the right timeout end time in all proceses, e.g. SystemUI/Settings

Expose AIDL method for LockPatternUtils, and use
PropertyInvalidatedCache for client-side caching which
can be invalidated by LockSettingsService.

Per-protector lockout end times are tracked by
SoftwareRateLimiter, which now receives hardware
timeouts.

Bug: 322014085
Flag: android.security.manage_lockout_end_time_in_service
Test: atest FrameworksCoreTests:com.android.internal.widget.LockPatternUtilsTest
Test: atest FrameworksServicesTests:com.android.server.locksettings

Change-Id: Icb87e2dc4d2b7c9070de1e85d15a74962f0d0663