Crawler: How to create the deprecation history of an already existing project

[BioPhoton]

For a new repository, the crawling process is pretty fine so far.
For already existing repository we need to run a bit different process.

The following assumptions are taken into consideration regarding the versioning and location of releases.

A list of release could be found in:
a) github releases
b) npm releases
c) ask the user to select a list of tags/release

For now, we start with c) and assume that a tag is the same as a release.

Preconditions:

• We can only crawl a branch of the target repo. No PR.

TODOS:

• Fetch all tags execSync('git tag').toString().trim().split('\n')
• Show all tags as multi-choice ordered by date
  • User selection step
• Crawl all selected branches
  • detect already crawled deprecations from older branches by the ruid (same ruid means already crawled earlier but not persisted)
  • 💡 Optionally crawl only the diff from 2 tags so we don't recrawl already crawled deprecations
• Persist the collected deprecations to the repo (master)
  • persist git tag and data to the deprecation object itself

[BioPhoton]

Closed in favor of #37