Apply rotation change on display thread

This aligns the same behavior as legacy that posts
continueDisplayChange to display thread.

Otherwise the display info change (triggered from
DisplayContent#updateDisplayAndOrientation -> setDisplayInfoOverrideFromWindowManager and then dispatch on
display thread) will reach client before window manger requests
resizing with buffer synchronization (shouldSyncWithBuffers).

This can also reduce about 10ms in WM lock because the display
thread is set to top-app sched group that usually runs on the
big core.

Also with this and [1] (transform hint), the workaround to force
full-blast-sync for 180 degree rotation is no longer needed.

[1]: Id4ad45adb9719b078f46040a09f786092c325a8a

Bug: 288105083
Test: Rotate device by 180 degree and observe display cutout
      doesn't show on opposite position.

Change-Id: I7e1de5b5fe12cb30b5f48808ea6b0a2214c0f339