WIP: Version npm package on release

[shrink]

npm's package.json requires a version parameter when publishing and so most npm projects include the version number in the project's package.json source code. However, most package managers don't require this and some go as far as to discourage it (see: composer.json) because it creates a relationship between source code and version, which should ideally be owned by the package manager.

A standard package-management workflow is possible using native npm features. The version command will set the version in package.json without committing using the no-git-tag-version argument.

dev:~$ npm --no-git-tag-version version 1.0.0

This composite GitHub action should:

1. Document why it isn't necessary to include a version in package.json
2. Fetch the version from the ref using battila7/get-version-action
3. Run npm's version cli command (without tagging)
4. Publish (optional, can defer to another action)

The workflow is very simple but uncommon in the npm world (I have not found an example) so the value of this project is more in educating people to this workflow, the functionality is very simple.