Rewrite ETIP as a GitHub repository

After a long thinking and experiencing various pain with the current version of ETIP (as well as seeing the same pain from many contributors), I'm wondering whether we could/should revamp totally ETIP another way.

Hear me out: what about switching to a GitHub repository with a specific file for each tracker. I'd expect Markdown or JSON format (but preferably Markdown to ease the review).

Name of the repository could be: https://github.com/Exodus-Privacy/trackers

**Advantages:**
* Each new contribution (tracker creation, tracker modification, tracker validation) can be discussed within the PR (see #106)
* Each new contribution (tracker creation, tracker modification, tracker validation) can be validated within the PR
* Everything about a tracker (its signature, name, etc.) can be discussed within an issue
* Every modification is visible through an associated PR
* Every past modification is visible through git commits (better transparency)
* We can have tracker validation within GitHub Actions (check for collisions, validate within the tracker is complete when validated, etc.)
* We could add administration rights to people outside the Exodus Privacy organization easily
* This removes the need to create account for everyone
* This removes the need to maintain the Django app (dependencies, etc.)
* This puts the focus on what matters here: the trackers details

**Drawbacks:**
* This requires a significant amount of work (writing scripts mostly) but I'm up for it if we go that way
* Probably harder to search for a specific tracker
* Everyone is required to have a GitHub account to contribute
* Each contribution needs to be reviewed before being merged (is it a drawback?)

This is a major change so I would love to hear your opinions @U039b @jawz101 @eighthave @blaueente @IzzySoft (feel free to tag any potentially interested person)