Utilize Atom's built in transpilation

[Arcanemagus]

Atom v1.13.0 introduced support for package's defining their own transpilation pipeline. Utilize this to remove the transpiled code from the repo and let Atom generate it on the fly.

NOTE: Based on the Task API branch, will need rebasing once #889 gets merged into master!

Fixes #857.

[Arcanemagus]

Note that this has a detrimental effect on the "activation time" (as TimeCop calls it) of the package since the transpiler engine must be loaded:

That's ~29 ms added due to this.

[Arcanemagus]

Filed atom/atom#14300 about the overhead from utilizing this. I still feel this is the direction we should go as it massively simplifies the code base, and the overhead there is coming from Atom itself.

[Arcanemagus]

Looks like Travis-CI and AppVeyor didn't like the base branch change, attempting a close/re-open.

[Arcanemagus]

I think the AppVeyor failure is due to atom/ci#66, will update to my test version of the script to check.

[Arcanemagus]

Hmm, that fixes the usage of the system node for installing the dev modules, but it's still failing as if it can't find the babel-preset-node5 module.

[Arcanemagus]

AppVeyor seems to have had a temporary issue causing the build to fail for a reason that should be completely out of their control, but changing nothing here has caused it to work properly.

On the plus side, I found that .babelrc was still in the project and have added removing that to this PR.

[IanVS]

This seems to work great, and you've gotta love that line count diff! This will greatly improve the dev experience working in this package, not worrying about running the compiler and checking in compiled code.

Big 👍 from me.