Expose the remaining resources in timeout error messages (#72)

[jmealo]

Implements #72

I tried to log errors straight away, however, that introduced stack traces for timeout errors which were previously omitted:

waiting for 6 resources: http://localhost:9333/bar, tcp:localhost:9333, http://localhost:9444/bar, tcp:localhost:9444, http://localhost:9555/bar, tcp:localhost:9666
waiting for 5 resources: http://localhost:9333/bar, http://localhost:9444/bar, tcp:localhost:9444, http://localhost:9555/bar, tcp:localhost:9666
waiting for 4 resources: http://localhost:9333/bar, http://localhost:9444/bar, http://localhost:9555/bar, tcp:localhost:9666
waiting for 3 resources: http://localhost:9333/bar, http://localhost:9555/bar, tcp:localhost:9666
waiting for 2 resources: http://localhost:9555/bar, tcp:localhost:9666
waiting for 1 resources: tcp:localhost:9666
wait-on(2656) exiting with error Error: timed out waiting for: tcp:localhost:9666
    at MergeMapSubscriber.project (/home/runner/work/fuzzy-winner/fuzzy-winner/node_modules/wait-on/lib/wait-on.js:129:1)
    at MergeMapSubscriber.module.exports.MergeMapSubscriber._tryNext (/home/runner/work/fuzzy-winner/fuzzy-winner/node_modules/rxjs/internal/operators/mergeMap.js:67:1)
    at MergeMapSubscriber.module.exports.MergeMapSubscriber._next (/home/runner/work/fuzzy-winner/fuzzy-winner/node_modules/rxjs/internal/operators/mergeMap.js:57:1)
    at MergeMapSubscriber.module.exports.Subscriber.next (/home/runner/work/fuzzy-winner/fuzzy-winner/node_modules/rxjs/internal/Subscriber.js:66:1)
    at AsyncAction.dispatch [as work] (/home/runner/work/fuzzy-winner/fuzzy-winner/node_modules/rxjs/internal/observable/timer.js:31:1)
    at AsyncAction.module.exports.AsyncAction._execute (/home/runner/work/fuzzy-winner/fuzzy-winner/node_modules/rxjs/internal/scheduler/AsyncAction.js:71:1)
    at AsyncAction.module.exports.AsyncAction.execute (/home/runner/work/fuzzy-winner/fuzzy-winner/node_modules/rxjs/internal/scheduler/AsyncAction.js:59:1)
    at AsyncScheduler.module.exports.AsyncScheduler.flush (/home/runner/work/fuzzy-winner/fuzzy-winner/node_modules/rxjs/internal/scheduler/AsyncScheduler.js:52:1)
    at listOnTimeout (internal/timers.js:531:17)
    at processTimers (internal/timers.js:475:7)

With the quick/nasty check in place now, we omit stack traces for errors that look like our timeout errors.

waiting for 6 resources: http://localhost:9333/bar, tcp:localhost:9333, http://localhost:9444/bar, tcp:localhost:9444, http://localhost:9555/bar, tcp:localhost:9666
waiting for 5 resources: http://localhost:9333/bar, http://localhost:9444/bar, tcp:localhost:9444, http://localhost:9555/bar, tcp:localhost:9666
waiting for 4 resources: http://localhost:9444/bar, tcp:localhost:9444, http://localhost:9555/bar, tcp:localhost:9666
waiting for 3 resources: http://localhost:9444/bar, http://localhost:9555/bar, tcp:localhost:9666
waiting for 2 resources: http://localhost:9555/bar, tcp:localhost:9666
waiting for 1 resources: tcp:localhost:9666
wait-on(2557) exiting with error; timed out waiting for: tcp:localhost:9666

[jeffbski]

Thanks @jmealo for taking the time to improve wait-on. I'll comment back here with the npm release it lands in.

[jeffbski]

https://github.com/jeffbski/wait-on/releases/tag/v5.2.0