Fix types

First release of git-db

Making sense of GitHub projects is harder than it should be.

1. Default insights are poor and do give us much information on how the project is evolving.
2. The API model is not straightforward (issues & PRs are handled together, some calls are easier on v3 than v4,...).
3. The typical approach consists on reading the API and computing metrics on-the-fly.
   This is too strict and new insights have a high cost (API calls).

Our goal with Git DB is to focus on simplicity and flexibility:

• We dump all the project's data to a local Duck DB.
• Your answers are one SQL query away.