Use travis to test and deploy

[grancalavera]

Under the assumption that:

• we'll use travis
• we'll npm version locally
• we'll publish with travis on tag
• we don't want to commit artifacts to git

Depending on:

• creating travis account Create travis account #18
• creating npm organization Create an NPM organization or an NPM private account #19

[mstade]

I'd actually prefer to use something like wercker down the line, but until they improve the workflow it's probably not worth it. The reason it's "better" is that we can have full control over the target environment, meaning we're not beholden to Travis CI quirks or lack of support.

This comment is mostly for posterity, such that if we revisit he CI / CD tool down the line there's something to kick off that discussion. Right now, however, I think we should just run with Travis.