And lo! a new release appears

This release exists thanks to the contributions of bug reports and suggestions from many people.
My thanks to all of them for their time to make git-version-bump better.

• If you have a need to force git-version-bump to report a particular version number, rather than derive it from the tags in the git repo, you can now do that by setting the versionBump.versionOverride and/or versionBump.dateOverride git config variables.
  The README has example commands for doing so.
  It should be vanishingly rare for anyone to need to do this, but the sorts of situations in which it might be useful are explained in the issue.

  Thanks to Roy Warps (@RoyWarps) for the feature request (#23), and the discussion that allowed us to come to an agreement on the right approach.

• The website URL in the gemspec now points somewhere useful (#14; thanks to Chris Miller, @iamchrismiller, for the report)

• Certain corner cases of version resolution going wrong when a GVB-using gem is being used in a different git repo are now handled better.
  Thanks to Dmitry Fleytman (@dmitryfleytman) for his original bug report (#13), and to Roy Warps (@RoyWarps) for his slightly differently structured bug report (#22), which between them helped me to identify and fix the underlying issue.

• The command that opens the text editor that allows you to write release notes no longer captures the terminal's stdout/stderr, so that terminal-based text editors don't get hung up. (#24)
  Thanks to Geff (@p64) for the report, PR, and patience in getting it into optimum shape.