Never ignore OCCLUDED transition

In an earlier attempt to cleanup some transition code, a check was
added to validate a transition request to make sure the "FROM" value
matched the existing state... a good idea. However, when exiting AOD
to launch camera a race condition existed that would result in
FromDreamingTransitionInteractor starting the transition
LOCKSCREEN->OCCLUDED. Previous code made a special case for this but
the new code ignored it, resulting in AOD over camera.

The new code updates conditions from both LOCKSCREEN and DREAMING to
make sure the device goes to OCCLUDED.

Fixes: 300406718
Test: atest KeyguardTransitionScenariosTest
Test: Tablet - Launch Home Controls over Dream, enter and exit
dreaming from LOCKSCREEN or GONE
Test: Phone - Test camera launches from AOD/DREAMING/LOCKSCREEN states

Change-Id: Ia3a90e650b34b5f480753b14398449cf51c42ce3