Fix apptest runner retry logic and output parsing.

Fix apptest runner retry logic and output parsing.

Fixing retry looping to bail on a success after a failure.
Only add valid gtest_filter flags when no filter is specified.
(don't try to filter using the 'mojo:apptest' name on crashes)
Make the GTEST output parsing agnostic to colored output.

BUG=509880
TEST=New Windows FYI bot retries failures/crashes as expected.
R=sky@chromium.org

Committed: https://crrev.com/8054d7869cb9e4022e63649a9335f46a80e3f7a7
Cr-Commit-Position: refs/heads/master@{#341994}

[msw, 2015-08-05 18:49:13]

Hey Scott, please take a look; thanks!

[sky, 2015-08-05 21:30:52]

LGTM - I think you're getting close to the point of wanting tests for this
script.

[msw, 2015-08-05 21:32:04]

On 2015/08/05 21:30:52, sky wrote:
> LGTM - I think you're getting close to the point of wanting tests for this
> script.

Yeah, I was thinking the same thing myself. I'll file a bug at least.

[msw, 2015-08-05 21:32:07]

The CQ bit was checked by msw@chromium.org

[commit-bot: I haz the power, 2015-08-05 21:33:19]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1269413003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1269413003/1

[commit-bot: I haz the power, 2015-08-05 22:48:35]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-08-05 22:49:27]

Patchset 1 (id:??) landed as
https://crrev.com/8054d7869cb9e4022e63649a9335f46a80e3f7a7
Cr-Commit-Position: refs/heads/master@{#341994}