Move displayId out of KeyguardState Transition object.

Since SystemUI/Shell can't access certain displays (e.g. private ones),
we won't be able to have shell choose which displays to send keyguard
state to - it will have to be delegated to Core which will choose to
send to all displays. Becuase of this, we will also change the call to
ATMS#setLockscreenShown instead, which already does the display
iteration for us.

This also changes the effect to EFFECT_LIFECYCLE, since
ATMS#setLockscreenShown potentially affects that (it does ensure
visibilty checks).

Test: atest
android.server.wm.multidisplay.MultiDisplayLockedKeyguardTests#testPrivateDisplayHideContentWhenLocked
Bug: 364930619
Flag: com.android.window.flags.ensure_keyguard_does_transition_starting

Change-Id: Ia367607c727c4fc8b9d2b636ecf54e86a84702fa