CLI: Upgrade node-watch to 0.7.4

[Krinkle]

Update node-watch from 0.7.3 to 0.7.4 (latest).

https://github.com/yuanchuan/node-watch/releases/tag/0.7.4
https://github.com/yuanchuan/node-watch/commits/master

• Verify npm publisher.
• Review package diffs.
• Stage update in PR and confirm releated features: CLI file watching.

Previously at https://github.com/qunitjs/qunit/issues/1522.

[Krinkle]

Verify publication: node-watch 0.7.4

Previously at #1524

$ npm info node-watch@0.7.1
node-watch@0.7.1 | MIT | deps: none

maintainers:
- yuanchuan <yuanchuan23@gmail.com>
- intervalia <intervalia@gmail.com>

Now:

$ npm info node-watch@0.7.4
node-watch@0.7.4 | MIT | deps: none | versions: 40

published 10 months ago by yuanchuan <yuanchuan23@gmail.com>

• ✅ It was published by the same account as previously.
• ✅ No new dependencies were added.
• ✅ No new dependencies were added.
• ✅ No dependencies changed.

LGTM.

Review package diff: node-watch 0.7.3 -> 0.7.4

https://diff.intrinsic.com/node-watch/0.7.3/0.7.4

• Minor change in type declaration (not used by QUnit).
• Calls to fs.watch() are now done via try-cach with an async error event introduced, to address Catch fs.watch exceptions yuanchuan/node-watch#125 and Fix can't listener error event on incorrect file/directory yuanchuan/node-watch#123. LGTM. I'm not aware of this affecting QUnit, but if it did, it looks like our existing way of calling it will pick that up nicely.
• ⚠️ Node 10 is declared as supported by package.json, but no longer covered by upstream CI. The PR that removed it from CI shows it as failing (logs have expired unfortunately) at 0.7.4 yuanchuan/node-watch#129.

Per the last point, I'll keep this off for now since there is no urgency for it. I only prepared this PR thinking it could go into the last QUnit 2.x release, but I'll let it go to 3.0 instead.