[Feature Request] Add support for extended file format

[a-raccoon]

There is no standard hash file format, but there are a few adopted defacto standards. Fortunately, all of the likely standards are pretty cross/backwards compatible and apparent. These are the formats I use, would prefer to use, and hope that HashCheck might support.

HashCheck already supports the following:

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
^ file merely contains a single hash value, no file path. use own filename to identify which file should be verified.

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF *\filename.doc
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF *x:\filename.doc
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF x:\filename.doc
^ file contains one or more hash values followed by qualified relative or absolute path. verify this/these files.
(don't ask me where the asterisk comes from. wish I knew. but HashCheck seems to support with and without.)

I'd also like it to support:

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 1234567890
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 1234567890 *\filename.doc
^ hash value followed by numeric value file size.  if the file size does not match first, verification fails.

this saves A LOT OF TIME having to verify a file when we know the filesize will not match. since
a numeric value is never a qualified path, we can always assume this means file size.

Enable the user to choose whether or not they want file sizes to be included in hash files. When HashCheck encounters any of these formats, it can automatically detect how to handle them given alphanumeric context.