un-bury file details

[tomchop]

In a test workflow, one artifact extraction produced 163 files, of which ~20 were "authorized_keys" files. They all show up in the same way (just the filename and file size) in the OR folder; there's no way to know at a glance where these are coming from in the disk image. It would be great to have a way to disambiguate which file comes from where. Some ideas:

• have the file details popup appear as one hovers over the filename
• have editable columns that allow to display a specific detail (I can see how this would be useful for hashes as well as file paths)

[berggren]

Good idea! If they are extracted from an image we store a reference to the image file, and the original path in the image as well. We can add that to the table.