Improved Outdated Response

This was the first, initial trial for a new response format for outdated
and installed.

npm tends to respond with some *very* weird output, as far as i am
concerned. If outdated or installed is called from the current
directory, and there is no package.json, npm won't fail at all. Instead
it will traverse up the tree looking for a valid project.

In the case of outdated, it will list outdated modules for the way
parent tree.

In the case of install, it will attempt to install the current directory
into the parent tree.

Both of these, in my opinion, are crazy and horribly unintended actions.
As such, the interface i am choosing is to fail if the given directory
is not a valid project.
Removed Directory from the Command

This is incorrect npm outdated usage, and i'm not really sure how to
explain the output. At any rate, removing the directory from the command
is correct usage, so i have done so.
Added CWD to Transports
For a brief moment FS and ChildProcess Rules

Made a handful of improvements to the code, and some additions to
the abstractions.

I *was* going to remove the transports abstraction, and instead use fs
and exec. Then i remembered that the target installations won't have
access to `kdc outdated`, so these fs/exec changes will be removed in
the soonafter commits.
Goodbye FS/Exec

Handful of improvements, and removed the non-transport plague from
our codebase. Huzzah!
Clean during Dev Test

During the normal dev test, we were not cleaning our build dir which was
causing issues for some of the tests (since they don't really clean up
after themselves in many cases). We now clear it before testing.
Increased Mocha Timeout

Until we properly mock npm (and to what degree will we.., i do not
know), i increased the timeout length so latency doesn't cause odd
failures.
Added --silent to Outdated Calls