Do something against the CircleCI timeouts

[ajafff]

Our mocha tests time out quite often on CircleCI. Especially node 0 which tests with node v4.x is prone to fail because it's slower than all other. It's annoying to always restart builds until one eventually succedes.

Some time ago I already increased the timeout for some test cases from 4000 to 8000 ms.
Do we want to increase the timeout further or try some other CI?

[adidahiya]

Which tests are slow? We should skip any tests which rely on an extended timeout (for now) and try to make them faster. I'd prefer to stay on CircleCI.

[ajafff]

I looked through the failed builds of the last weeks. We have a winner: It's the test for tslint --project --fix.
There are some other IO heavy tests that fail occasionally, but >90% of the time it's the first one in the list:

• Executable --project flag can apply fixes from multiple rules (8000ms)
• Configuration loadConfigurationFromPath with config not relative to tslint extends with package installed relative to tslint (2000ms)
• Executable --project flag works with '--exclude' (4000ms)
• Linter apply fixes to correct files (2000ms)

Possible fix for the first list item: use runner.ts directly instead of spawning a new process. That avoid loading all sources and (de)optimizing them again. Related: #2587