Update KeyguardUpdateMonitor DPM_STATE_CHANGED params

KUM#DPM_STATE_CHANGE was sending the userId as message's object obj,
not arg1, so this test would break on headless system variants since
msg.arg1 always was equal to 0 (while this always passes on non-headless
systems since the test always runs as userId 0).

Test: atest KeyguardUpdateMonitorTest#testSecondaryLockscreenRequirement
on a headless system device variant (previously was 100% failing)
Fixes: 264869291

Change-Id: Iab519b59ca92ea25da1386cb2e020df63c828070