Instead of artifical timeouts and race condition in waiting
for snackbar's dismissal in a loop, use Espresso's IdlingResource
to reliably wait until the snackbar has been shown or
dismissed.
Also align the API surface of snackbar's callbacks with DrawerLayout's
listeners, allowing registering more than one callback, and removing
registered callbacks.
Bug: 32022732
Test: ./gradlew support-design:connectedCheck --info --daemon -Pandroid.testInstrumentationRunnerArguments.class=android.support.design.widget.CustomSnackbarTest
Test: ./gradlew support-design:connectedCheck --info --daemon -Pandroid.testInstrumentationRunnerArguments.class=android.support.design.widget.SnackbarTest
Change-Id: If8f8415b6453d75cb24a022b2d7d676f7649542c
GitOrigin-RevId=8c153ac8980737c4292ae1c019c69471607b3859
PiperOrigin-RevId: 141502000
This CL will look a bit strange, as it reverse some changes that
were already present. Unfortunately the Android auto-merger greatly
confuses our syncing tool, as it effectively creates new commits
that have the same content as old commits, and does so in a
non-linear fashion (e.g. the commit tree in 25.1.0 is not merely
built on top of 25.0.1).
This CL will get us into a state where we're ready to apply the rest
of the 25.1.0 changes in succession, and once that is completed,
we'll be at the correct (matching) state.
GitOrigin-RevId=11a895a323af06c4731e4c64a7ec2c09ac0aaf2f
PiperOrigin-RevId: 141497561
This new structure will allow for a top-level gradle file and a multi-project
build (which is a more typical structure for things). In the future, it will
allow us to place other projects in here as well (such as sample applications).
PiperOrigin-RevId: 141247594
