Add more robust release scripts

[levithomason]

The current release script always increments the minor to publish. Then it increments the patch but only pushes to github.

The new scripts allow for releasing major, minor, or patch explicitly. Additionally, there are safeguards if you're not logged into NPM or if you do not have write access as a collaborator. These prevent you from accidentally bumping/tagging/committing/pushing and then failing on publish.

Not logged in

When not logged in, prevent bump/tag/commit/push success with publish fail:

› npm logout
› npm run release:patch

You must be logged into NPM to publish, run "npm login" first.

No write access

When not a contributor with write access, prevent bump/tag/commit/push success with publish fail:

› npm run release:patch

fakeuser does not have NPM write access. Request access from one of these fine folk:

finnpauls <derfinn@gmail.com>
levithomason <me@levithomason.com>
mikeal <mikeal.rogers@gmail.com>

All is well

If all is well, go for it:

› npm run release:patch

Publishing new patch version as levithomason.

npm version patch
git push
git push --follow-tags
npm publish

---

Prevent bad direct use

The bash release script will not be used directly, however, if it is used directly and improperly then it will show the proper usage:

› bash scripts/release.sh invalid-version

  Usage: bash scripts/release.sh <major|minor|patch>

[levithomason]

The new scripts for releases.