Add context info about binary files that are being hashed

[csasarak]

Overview

We will sometimes encounter an error when fingerprinting binary files. Previously we didn't log the filename of the file being hashed in our debug bundle. This PR adds that context.

Acceptance criteria

• There should be filename info in the debug bundle for each file that is fingerprinted.

Testing plan

Manual, this is a change to logging/reporting only.

References

• ANE-1855: Show file paths when error is throwing trying to open file

Checklist

• [x] I added tests for this PR's change (or explained in the PR description why tests don't make sense).
• [x] If this PR introduced a user-visible change, I added documentation into docs/.
• [x] If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
• [x] If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an # Unreleased section at the top.
• [x] If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
• [x] If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.