verify_sfv fails files with lower case crc32 strings even though the crc32 is technically a match

[earandel]

Sometimes sfv files don't have the crc32 string in upper case hexadecimal but rather in lower case hexadecimal. When this happens, file hash.verify_sfv returns failed matches even though the crc32 expected vs actual is technically correct. Should the check be:

expected_crc32.upper() == actual_crc32.upper()

to be more resilient/forgiving?

[earandel]

verify_sfv also fails with some sfv files that always generate an 8 character crc32 string with leading zeros to pad to 8 characters as needed. The filehash module drops leading zeros so expected value and actual value don't match.