Use grunt-release to automate releases

This is what I was thinking to simply the current release process. A any future releases would go as follows:

- Ensure origin/master has all the changes for the upcoming release
- Ensure local/master is up to date with origin/master
- run `grunt release:(patch|minor|major)` to release patch, minor, or major releases respectively

Running the above command will do the following:

- Update the version string in `package.json`
- Commit the new `package.json` file
- Create and push a git tag for the new version
- Publish the new version to npm

For what it's work I use this in all my personal and work projects.