Separately timing out different power groups

An issue was observed that even though the power groups timeout was
configured differntly, they would lock/unlock together. This was
primarily because PhoneWindowManager invoked KeyguardDelegate only when
the default display was sleeping/waking up. This condition has now been
updated to instead check on the global interactivity.

We also noticed issues that the system would block the migration of the
display from sleeping to dozing state, this has now been relaxed for the
cases where there are more than one power groups and all of them are
sleeping

The system will now sleep the default display when it times out if there
is another active power group. This will then transition to doze when
all the non-default power groups migrate to sleep

This CL was originally reverted because of b/419803718. This is because
once the display transitions from Dream to Off, we wouldnt notify the
DozeService to activate the TriggerSensor, which impacted the tap to
wakeup gesture in certain cases.

Bug: 414444200
Test: Manual
Test: atest com.android.server.power
Flag: com.android.server.display.feature.flags.separate_timeouts
Change-Id: Ic6b1f4c60e12bd510e3629aee7d5edb7d67af10e