blake3 checksum files are incompatible with reference implementation

[Ost3rbaer]

The reference implementation from https://github.com/BLAKE3-team/BLAKE3 can not verify blake3 hash files generated by RapidCRC for two reasons

• it does not like asteriks before the filenames, only double space between hash and filename is accepted as separator
• it does not cope with DOS style line endings, only LF is accepted as separator

One could consider this as a flaw of the reference implementation, but non-binary files are meaningless in the UNIX world.

When checking "create UNIX style hash files" under options, the output uses LF line endings (good) but file names are still preceeded by asteriks (bad).

RapidCRC should generate compatible files when the compatibility option is selected.

[OV2]

This was implemented before the official b3sum had any check support, and I simply used the same format as md5/shaX. I've pushed a commit to always write .blake3 files without a *.

[tERyceNzAchE]

I agree with @Ost3rbaer that this change should only be when the option is checked, and the current behavior maintained otherwise. The currently generated files are compatible with HashCheck, which is the other very popular Windows program for generating hashes.

[OV2]

HashCheck can also read files without a , so it should be ok to create all .blake3 files without the in the future.