feat: detect checksum files based on file extensions

[Integral-Tech]

Summary

Detect checksum files based on suffixes.

Closes: #181

Type of change

• Bug fix
• Feature
• Refactor
• Breaking change
• This change requires a documentation update

Test plan

todo

[ifd3f]

Just wondering, haven't looked much into this PR yet, will this conflict with #184?

[dbohdan]

#184 makes minimum changes to find_hash besides renaming it, so this PR should be easy to rebase.

[ifd3f]

Ran it locally and it looks good.

% cargo run -- burn duo256_sd.img
   Compiling caligula v0.4.8 (/home/astrid/Documents/caligula)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.33s
     Running `target/debug/caligula burn duo256_sd.img`
Input file: duo256_sd.img
Detected compression format: no compression
> Is this okay? Yes
> Detected hash file duo256_sd.img.sha256 in the directory. Do you want to use it? Yes
Disk image verified successfully!
? Select target disk  
> <Refresh devices>
  <Show all disks, removable or not>
[Only displaying removable disks.]

I like the feature, but I'd prefer if you just made a separate array for extensions, and separated out the logic accordingly. Something like this:

const HASH_FILES: &[(HashAlg, &str)] = &[
    (HashAlg::Md5, "md5sum.txt"),
    (HashAlg::Md5, "md5sums.txt"),
    (HashAlg::Md5, "MD5SUM"),
    ...
];

const HASH_EXTENSIONS: &[(HashAlg, &str)] = &[
    (HashAlg::Md5, "md5"),
    (HashAlg::Sha1, "sha1"),
    ...
];

pub fn find_hash(input: &Path) -> Option<(HashAlg, String, Vec<u8>)> {
    for (alg, hash_file) in HASH_FILES {
        ...
    }
    for (alg, hash_file) in HASH_EXTENSIONS {
        ...
    }
}

[Integral-Tech]

@ifd3f Resolved :)

[ifd3f]

Thanks! Will go merge and resolve conflicts when I get the chance.

[Integral-Tech]

@ifd3f Conflicts resolved :)