Revert r159735 - support for test harness (text-only) tests w/o expected results

It turns out that js-test-post.js will print out "PASS successfully parsed"
and so it's possible for a js-test to be considered passing even if there
are no actual assertions and no -expected.txt files. This is, at best,
confusing.

I'm reverting this change until I can change the testharnessreport.js
scaffolding to print out something more distinctive so we can be sure we're
getting the PASS/FAIL behavior and interpreting it intentionally. We don't
really need this change for now (or until we start running the w3c tests
regularly).

R=esprehn@chromium.org, ojan@chromium.org
BUG=268711

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161205 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add missing baselines added before r161205 landed

(This was while we were letting tests go w/o -expected.txt files.

Also, fix a typo in print-json-test-results.

TBR=esprehn@chromium.org

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

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