cc: Make re-added animations get pushed to the compositor thread

cc: Make re-added animations get pushed to the compositor thread

When a layer with an animation is removed from the tree but later
re-added (this can happen, for example, when an iframe containing
an animation is set to display:none and later set back to
display:block), the animation should continue. Currently, the
animation is prevented from getting re-pushed to the compositor
thread since it already has a start time. This logic used to be
needed to prevent incorrectly re-pushing an animation that had
already been deleted  on the compositor thread, but is no longer
needed for that purpose since we now always delete animations on
the main thread before deleting them on the compositor thread.
This CL removes this logic.

BUG=409649
Committed: https://crrev.com/04063aa44f0b20829ae07663da96eba19ebe8f38
Cr-Commit-Position: refs/heads/master@{#330938}

[ajuma, 2015-05-21 13:06:37]

ajuma@chromium.org changed reviewers:
+ vollick@chromium.org

[Ian Vollick, 2015-05-21 14:25:27]

On 2015/05/21 at 13:06:46, ajuma wrote:
> 

nice! lgtm.

[ajuma, 2015-05-21 14:26:57]

The CQ bit was checked by ajuma@chromium.org

[commit-bot: I haz the power, 2015-05-21 14:27:33]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1148333002/20001

[commit-bot: I haz the power, 2015-05-21 14:30:52]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-05-21 14:31:40]

Patchset 2 (id:??) landed as
https://crrev.com/04063aa44f0b20829ae07663da96eba19ebe8f38
Cr-Commit-Position: refs/heads/master@{#330938}