Implement multi-core fuzzer

[devatwork]

Refactor the fuzzer implementation into the engine and the
corpus_based_fuzzer components. This allowes multiple fuzzers
to co-exist side-by-side.

The engine is overhauled to support running on multiple core in
parallel. Big shoutout to @mvanbutselaar for his help with the
implementation. The output of the engine is colorized for improved
readability.

[DrRataplan]

BundleMon

Unchanged files (2)

Status	Path	Size	Limits
✅	fontoxpath.esm.js	88.68KB	-
✅	fontoxpath.js	88.58KB	-

No change in files bundle size

Final result: ✅

---

Current branch size history | Target branch size history

[coveralls]

Coverage remained the same at 95.707% when pulling 67c1780 on threaded-fuzzer into 6d52b43 on master.

[devatwork]

@DrRataplan Not sure how to deal with the 2 remaining CodeFactor issues. @mvanbutselaar and I needed to alias the Worker class to ThreadWorker, so in my opinion both the casing is correct (because it is a type alias for a class) and the use of the spread operator for the aliasing. Any suggestions?

[DrRataplan]

I guess a big part of why the code is not deemed up-to-par is because of the mixed import and require. Using more import as should make this better. Did you already try that?

My linter immediately warned me about the mixed imports/require. Consider making tslint work, it helps in the long run. I'll push a fix

[devatwork]

Thanks, my linter is seriously fubar and my TS skills are not up to par yet. Thanks for making the changes and maybe at some point we can jointly fix my linter because these issues waist both our time.