fedcode-next: Collect fix commits from pre-existing datasets

[pombredanne]

We should focus on the database of manually reviewed fix commits and avoid automated fix commits.

OSV fix commits:

• Add support for git version ranges #767

Databases Requiring Review:

1. project-kb:

• https://github.com/SAP/project-kb/tree/vulnerability-data
• https://github.com/SAP/project-kb/tree/main/MSR2019

2. vulncode-db (to be considered later after review, the project is archived now)

• Collect fix commits from https://github.com/google/vulncode-db/  #118

3. linux_kernel_cves

• Import data from https://github.com/nluedtke/linux_kernel_cves #564

4. Morefixes:

• https://github.com/JafarAkhondali/Morefixes

5. MSR_20_Code_vulnerability_CSV_Dataset
   https://github.com/ZeoVan/MSR_20_Code_vulnerability_CSV_Dataset

6. GNU Libc fix commits

• Add glibc advisories #1362

7. Android fixes from

• https://github.com/quarkslab/aosp_dataset

related issue

• fedcode-next: Collect existing fix commits and patches open datasets #1697

[ziadhany]

this is done now, we are collecting fix commits from

OSV data:

• Fix OSV to handle affected_packages correctly & add support to collect commits #2080

project-kb:

• Migrate Importer to Advisory v2 & Collect Existing Fix Commits for Project KB #1987

linux_kernel_cves:

• Collect existing fix commits for Linux Kernel #1989

GNU Libc fix commits:

• Add support for glib importer #2118

Android fixes from:

• Add support for introduced and fixed commits in AdvisoryData #2017