purl-next: Deploy PurlDB database - git backends

[pombredanne]

Deploy PurlDB database git backends.

For this we need to:

• purl-next: Revisit the hashid approach and how many git repositories we have for each ecosystem #747
• Abstract git repo handling in base MineCodeBasePipeline #750
• Refactor mine_nuget to use MineCodeBasePipeline for git deployment #780
• Refactor mine_cargo to use MineCodeBasePipeline for git deployment #770
• Refactor mine_alpine to use MineCodeBasePipeline for git deployment #774
• Refactor mine_maven to use MineCodeBasePipeline for git deployment #777
• Refactor mine_conan to use MineCodeBasePipeline for git deployment #773
• Refactor mine_composer to use MineCodeBasePipeline for git deployment #772
• Refactor mine_swift to use MineCodeBasePipeline for git deployment #779
• Refactor mine_debian to use MineCodeBasePipeline for git deployment #776
• Refactor mine_cran to use MineCodeBasePipeline for git deployment #775
• Refactor mine_cpan to use MinecodeBasePipeline for git deployment #793
• Refactor mine_pypi to use MineCodeBasePipeline for git deployment #778
• Refactor mine_npm to use MineCodeBasePipeline for git deployment #798

[JonoYang]

We need some functions to

• Clone a data repo that contains purls for package ecosystems (e.g. https://github.com/aboutcode-data)
• For each purl.yml file, create a package in the packagedb based on those purls