Add pipe and step to "fix" or "resolve" errors automatically OR avoid scanning errors in the first place

From https://github.com/nexB/scancode.io/issues/338#issuecomment-941006058

We could have a way to resolve errors with a new "resolution" field that would store a resolution note when the error is resolved. For instance this kind of error:
```
ERROR: for scanner: licenses: ERROR: Processing interrupted: timeout after 120 seconds.
id: 21457001
md5: 43e47161986663a8d308c08907c21931
name: TestListSkus
path: azure-sdk-for-net-64c6c3b957bd22fb0664bb3b7500c046aaa87ddc.zip-extract/azure-sdk-for-net-64c6c3b957bd22fb0664bb3b7500c046aaa87ddc/sdk/compute/Microsoft.Azure.Management.Compute/tests/SessionRecords/ListSkuTests/TestListSkus.json
```
could be resolved automatically as "not important" as this is a large (15MB) JSON data files that times out, and is further a test file.

There are several other common cases that could be easily be fixed without human intervention and this would reduce the noise.

An alternative design could be to avoid entirely certain of errors. In the case above, this would mean skipping scanning a large data file used in tests. Or skipping scanning test files entirely or data files entirely