integrityCheck and DROID reports that scanned inside containers

[DavidUnderdown]

Similar to #68 if you have a DROID report that includes rows for files that are actually inside ZIPs or other "archival" containers this causes problems with the integrityCheck feature. I tried to filter out these rows from checks such as fileExists and integrityCheck by using an if statement and checking that the URI does not start with zip: or sevenz: or tar: etc which indicate the presence of an archival container, as CSV Validator cannot read inside the container, but then integrityCheck fails to detect (ordinary) added files and folders.

See https://github.com/digital-preservation/droid-csv-schema/blob/master/DROID_integrity_check.csvs for example