Set bounds on all new motion controllers

[zsoltk]

Description

Observed bug

Sample app scenario:

1. Moved Promoter to inside Spotlight, rather than BackStack
2. Embedded component works at first, but when moved off screen then re-added to composition, it looks visually broken

Why this happens

1. With BackStack, Promoter was popped and recreated the next time; however, with Spotlight it was kept alive

2. The embedded AppyxComponent receives updateContext when re-entering the composition

3. This leads to its MotionController being recreated (without any knowledge of TransitionBounds)

4. Since the component cached the last TransitionBounds, and the new one passed to it is exactly the same, the if check does not set it on the new MotionController instance:

   override fun updateBounds(transitionBounds: TransitionBounds) {
       if (transitionBounds != this.transitionBounds) {
           this.transitionBounds = transitionBounds
           _gestureFactory = gestureFactory(transitionBounds)
           _motionController?.updateBounds(transitionBounds)
       }
   }

   Which is fine that it's skipped, but we shouldn't rely on this being called either.

5. If the size of the bounds is used to calculate any TargetUiState values (as is the case with Promoter), those will be messed up.

Fix introduced

Always set bounds on the new MotionController instance.

Check list

• I have updated CHANGELOG.md if required.
• I have updated documentation if required.