vellum changes

Update to built version of latest master of http://github.com/mwhite/Vellum, which fixes all issues I'm aware of.  As in, I think it's production-ready if you can't find any more bugs.

You'll want to do at least a sanity check on the other multimedia upload related stuff, since this changes the delivery of the mutual dependencies (adding a submodule).

Process as described in the README there is to download an automatically-built archive of the built files from drone.io and extract to a folder in HQ.  As in, this removes the Vellum submodule, without adding anything to the HQ build script.  I suggest making a bash alias for this so it doesn't seem like more work than updating a submodule reference.

If you change `settings.VELLUM_DEBUG` to True, you can run the non-built version of Vellum in HQ.  It's expected to be cloned in submodules/vellum/Vellum.

However, seeing as basically everything except uploading multimedia and saving a form to HQ can be tested in the test page, I highly recommend just using that.  It's still deployed automatically to http://vellum-master.herokuapp.com and on pull requests.  It defaults to using the non-built version on localhost and the built version otherwise.  You can override this by appending ?built or ?async.  Will make some links for this on the test page.

There are a few minor non-blocking issues with the RequireJS setup that should be addressed at some point: https://github.com/mwhite/Vellum/issues/112

I've enabled Travis on my repo with just JSHint for now, and will be re-hooking up the existing tests once I write some tests for my upcoming changes.  

Hopefully now we can switch to doing incremental PRs off my master, which can get acceptance testing on the PR, and which I can then review pretty effectively for defects since I've read and touched the entire codebase many times by now, and then you can do whatever you want for regression testing and submit bugs as Github issues.