`tag` command to support non-node/package.json version checks

[woozyking]

currently, the release tag command assumes the source of repo project version is from package.json which is usually seen in the node.js ecosystem.

in order to support (or not fail in) other language stacks/context, we should probably provision a flag to suppress the check or defer the duty of matching version from commit message and local package versioning, such as:

% release tag --version='<version>`

where <version> can be:

• skip - so the version matching check is skipped altogether.
• an exclusively supplied value - where we defer to the CLI users to parse and extract the version from local repo context (such as Python package's __version__ value) and use that to perform a matching check against commit message extract version.