fast-scan: Create scan benchmark for package detection in ScanCode Toolkit

[pombredanne]

The package detection benchmark should be based on real case and not made up data. We should have at least a package for each type, and cases with and without nested package files, deep dependencies and complex licensing.

We would need to have:

• Details of data/repos/files used for benchmarking
• Simple instructions to run the benchmark
• Document the issues we found

[AyanSinhaMahapatra]

Related issues:

• Package assembly is extremely slow for PythonInstalledWheelMetadataFile handler with many package resources #4167
• package assembly in inspect_packages and other pipelines is too slow scancode.io#1398

... therefore package "assembly" is a likely candidate

[chinyeungli]

fast-scan-package_scans_benchmark-list.csv

@AyanSinhaMahapatra I have created a list that could potentially used as the benchmarks for package scan. Please take a quick look to see if it's alright and I'll do the download and launch the package scan.

[chinyeungli]

@pombredanne please check fast-scan-package_scans_benchmark-list.csv

(Also at
https://docs.google.com/spreadsheets/d/1A4g6LvP1s-DuBI1_Ev_hJuQ81bTTkMzL/edit?usp=drive_link&ouid=111292578521869099532&rtpof=true&sd=true )

if these are the things that we want to look at. There are basically 3 items that I look at:

1. "for_packages" coverage
2. detected license
3. different purls in same repo

Since these tasks are entirely manual, perhaps doing a few of each type is sufficient?