Enqueue ATMS calls before display callbacks.

For currently mysterious reasons, the display callbacks can take up to 1000ms to run, and due to a Handler#runWithScissors call in TrustManager, this can block the ATMS lockscreen calls, resulting in unlocked app content being visible under the lockscreen for some time.

I don't know what will happen if we invert the order here. It seems to work fine, but let's see what presubmits have to say.

Bug: 399693427
Test: manual
Test: presubmits pass
Flag: com.android.systemui.keyguard_wm_reorder_atms_calls
Change-Id: I9ecca8cd2125b3d7b791f17b639417b2b7f4c14c