Fix stack bounds when requesting pulsing on AOD

When AOD is enabled, and we are requesting pulsing, a new transition
starts from GONE to AOD. At the end of this transition we receive
multiple steps, where the progress is 1.0f. This breaks the
interpolation, and sends invalid bounds to the NSSL.

Fixes: 346557361
Test: atest SharedNotificationContainerViewModelTest
Test: go to AOD, receive a HUN (pulsing), observe the HUN's position
Flag: com.android.systemui.migrate_clocks_to_blueprint
Change-Id: I9b922834b6378183738bf7c301ad947bfafa076d