Get file context from frictionless validation errors

[karlcz]

When we collect the frictionless validation report, we seem to lose the processed file context for some (if not all?) individual data resource errors. This makes the diagnostic information less meaningful in the portal UX.

An example:

Found 246 errors in datapackage “C2M2_datapackage.json”. First error: There is an extra label “” in header at position “11”

In this case, the TSV formatting error was for the subject.tsv file.