Revert of Introduce NON_ZERO_DURATION for animation unit tests

Revert of Introduce NON_ZERO_DURATION for animation unit tests (https://codereview.chromium.org/420013002/)

Reason for revert:
I suspect this is causing Linux Tests dbg (2) failures in app_list_unittests:
http://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%282%29/builds/47929

Strangely I had green try runs for linux_chromium_rel for app_list_unittests.


Original issue's description:
> Introduce NON_ZERO_DURATION for animation unit tests
> 
> Animations are usually disabled in unit tests for performance. However, to
> test the animation system itself some tests request "normal" durations.
> Under some conditions (remote desktop, animation disabled for accessibility)
> the "normal" duration could still be zero.
> 
> This was causing test failures and use-after-frees in ash_unittests on the
> drmemory bots and for developers using remote desktop.
> 
> Introduce NON_ZERO_DURATION to signal that animation must be enabled and the
> duration must be non-zero, but other than that can be as short as possible.
> 
> BUG=397478, 396969
> TEST=ash_unittests on drmemory, Windows and Chrome OS bots
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=286089

TBR=oshima@chromium.org,ajuma@chromium.org,sky@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=397478, 396969
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=286102

[James Cook, 2014-07-29 05:02:48]

Created Revert of Introduce NON_ZERO_DURATION for animation unit tests

[commit-bot: I haz the power, 2014-07-29 05:04:25]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jamescook@chromium.org/413403011/1

[commit-bot: I haz the power, 2014-07-29 05:06:27]

Change committed as 286102