Use separated display transaction

Since new transition system is enabled in U, the display will
use its own transaction to play animation. So it is no longer
appropriate to use a global transaction to update all displays.

Otherwise the order of transaction may apply old state, e.g.
Display1 is rotating and Display2 is resizing, the transaction
T1 may contain the new rotation for D1 and old size for D2. And
the transaction T2 contains new size for D2. If T2 is applied
before T1, the Display2 will still show with old projection.

Also removed the traversal when updating rotation because
RWC#applySurfaceChangesTransaction will always be called
before starting the transition. Then only need to keep one
centralized invocation entry.

Bug: 322121097
Test: CtsWindowManagerDeviceDisplay
Change-Id: Icefa9e9810996a3e5fbe95bfea2a2aebc044cdce