chore(package): add standard-version as npm run release

[nexdrew]

A better alternative to npm version.

[bcoe]

the march towards proper semantic versioning continues.

[nexdrew]

@bcoe Just as an aside, I know you have used "version" as the script name in a couple places, but the reason I prefer "release" is to avoid the ambiguity of npm run version vs npm version (in the case that the author forgets that custom scripts require npm run <script> and not just npm <script>, as I have done many times before).

npm release has no meaning and thus prints help text and exits with code 1 whereas npm version has meaning and exits with code 0.

Let me know if you're strongly persuaded one way or the other. Thanks.