Tests: Fix bad test case that always passes

Follows-up #1335, which was missing
the quotes on the tap-outputs key, and thus the unit test was seeing
expectedOutput[command] as `undefined`, which was then passed to
RegExp as `new RegExp(undefined)`, which produces /(?:)/, which is a
no-op that always matches, so re.test(output) === true.

Yay me for writing a useless test.

Ref #1333.

test/cli/fixtures/expected/tap-outputs.js

@@ -52,7 +52,7 @@ ok 2 Second > 1
 # todo 0
 # fail 0`,
 
-	"qunit 'fail/throws-match.js'":
+	"qunit fail/throws-match.js":
 `TAP version 13
 not ok 1 global failure
   ---