Updating rotation transaction behaviour

- Ensure we use the final animation bounds to calculate the bounds in
  the new orientation if there is an animation running
- If there is an transition animation running during rotation, we need
  to cancel the animation and not schedule any WCT updates separate from
  the transaction passed to the display change listener.  For this
  transaction, we specify the bounds change + a surface transaction for
  the new bounds in the next orientation.

Bug: 159397143
Test: atest PinnedStackTests
Test: Enter pip in portrait, hold the phone in landscape physically and
      launch apps + go home repeatedly

Change-Id: Ib473654bd0e55492b2bc803faea6825db440bf13