Automate release process

[jhollingworth]

Forgotten to re-build twice now. Need a single command that

• Reminds me to update history.md
• Inc's marty-lib version, rebuilds, pushes (inc. tags) and npm publishes
• Updates marty & marty-native dependencies to use new marty-lib version
• Rebuilds marty and marty-native, updates version, pushes (inc. tags) and npm publishes

[taion]

As part of this, it might make sense to merge the marty-lib and marty repos, so we have one place for code/issues/PRs/&c.

Something like have all the code be the marty-lib code, and deploy marty and marty-native from separate directories within the repo, plus automatically update separate GH repos for the Bower packages as part of the release process.