Fix handling of tests that fail two different ways in run-webkit-tests.

This is a follow-on to r159630. It turns out I wasn't covering the
case where a test fails two different ways, and the second failure
is actually an expected failure.

Also clean up the testing logic a bit and make sure print-json-test-results
is updated w/ the correct parsing logic (cloned downstream in
build/android/bb_device_steps.py).

Note that the code was working correctly, but the tests were bad. This change fixes the tests but does not change the code.

R=ojan@chromium.org
BUG=307277

update tests

Review URL: https://codereview.chromium.org/27369006

git-svn-id: svn://svn.chromium.org/blink/trunk@159977 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Assume coords of (0,0) for simulated clicks on <input type=image>

Activating an image button with the keyboard or element.click() should
result in selected coords of (0,0). This is consistent with the spec and
IE and Firefox.

The relevant spec is:
"If the user activates the control without explicitly selecting a
coordinate, then the coordinate (0,0) must be assumed."
http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#image-button-state-(type=image)

WebKit also had this behavior until
http://trac.webkit.org/changeset/136280

BUG=306392

Review URL: https://codereview.chromium.org/27667002

git-svn-id: svn://svn.chromium.org/blink/trunk@159978 bbb929c8-8fbe-4397-9dbb-9b2b20218538