feat: Add TypeScript local resolving

[Maecenas]

Fix and extend #765

Changing { paths: [cwd] } (BTW, is this by design?) to { paths: [cwd, __dirname] } would make ts-node able to resolve both local and global typescript dependency.

[coveralls]

Coverage remained the same at 86.082% when pulling 2d57c9a on Maecenas:patch-1 into c2ecc7d on TypeStrong:master.

[blakeembrey]

@Maecenas This seems reasonable. I was hesitant to support this since it makes resolution a little unpredictable. What are you thoughts on doing this by default vs behind a flag?

[Maecenas]

@blakeembrey The motivation is to contribute ts-node to Homebrew. It seems ts-node is resolving typescript from local ($ npm i -D), and then global ($ npm i -g). As for Homebrew, apps are installed to a path /usr/local/Cellar and can not trace seperated local dependency.

The intuition behind this PR is to add installed path to dependencies resolving, as __dirname and after cwd yet before global path.