2.0 Rewrite: SHOULD HAVE features

[JKrag]

This is the total scope of features that should be implemented. Must be broken down to smaller issues later.

Usage:
  #{__FILE__} --latest=<tag-glob> [options]
  #{__FILE__} <ref>               [options]

Options:
  [-v | -vv | -vvv]

    More verbose output (counteracts -q option)
    
  [-q | -qq | -qqq]

    Less verbose output (counteracts -v option)
    
  -l --latest=<tag-glob>

    Specify a glob pattern to search for last matching tag instead of
    providing a specific ref.
    Will attempt to use everything after <tag-glob> as the version string
    so be sure to provide _entire_ prefix.
    E.g. use "R_" if your versions are "R_1.2.3"

  -t --tag-commit  Actually tag HEAD with the version number computed.

  -p --prefix=<prefix>

    Specify a prefix to add before the resulting version string

  --postfix=<postfix>

    Specify the "special" part of the resulting version string.
    This is any  part of the version string that comes after the dash,
    e.g. in 1.3.4-SNAPSHOT it is the string "SNAPSHOT".
    Note this is for the "output" side.
    PlusBump will accept any special string on the input and preserve it,
    unless you specify `--special=""` or something else.

  --majorpattern=<major_pattern>

    Specify an alternative (regex) pattern that indicates a major version bump.
    E.g. --majorpattern='\\+major'

  --minorpattern=<minor_pattern>

    Specify an alternative (regex) pattern that indicates a minor version bump.
    E.g. --minorpattern='\\+minor'

  --patchpattern=<minor_pattern>

      Specify an alternative (regex) pattern that indicates a minor version bump.
      E.g. --minorpattern='\\+minor'

[JKrag]

Maybe we also want to add --version to this list