Ensure dim changes are in same transaction; do not wait for token to change visibility

- Use the pending transaction to avoid collecting changes to the same
dim in separate transactions. This was causing problems since
multiple WindowStates can request a dim change, and they were doing so
by placing the changes in different transactions. This was an issue since there was
no guarantee that they were then merged in the correct order.

- Check for the requested visibility of the token to avoid waiting for it to change its visibility at the end of a transition. This allows to
shield the dim from changes to its windows while it waits to be
committed.

Fix: 288863491
Test: DimmerTests
(cherry picked from commit af7f6b22)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:ffd12608371aaaf9b4754353c950f05c6601935b)
Merged-In: I96f8d1b091dd0f897c50833be7540b00fa2ead70
Change-Id: I96f8d1b091dd0f897c50833be7540b00fa2ead70