Add logging library to properly capture errors

[chrisahardie]

Introduce winston for logging, will stop console messages from being emitted during test runs!

[jennygrahamjones]

Is the intention to make wider use of the logging, or just to suppress the console messages during tests? If the latter, the --silent flag could be added to the test command.

[chrisahardie]

@jennygrahamjones The optimal solution would have been to leverage Winston and vary its transports by environment, with our non-dev environments writing logs out to an external provider like Sentry, Bugsnag, or something similar. The console error messages being suppressed would have just been a small bonus.

If you want to add a --silent flag, that would be fine. I don't anticipate we'll stand up remote logging (though it would be useful if we ever wanted to platform FYI @picuron ... )