POI Dispute service

[goaaron]

Code here is an MVP for automating the process of collecting indexer data,generating divergent blocks and matching events, and using those to determine a root cause for POI mismatch. This is one part of the tool, the other part is a subsequent PR against graph-node.

Workflow goes like this (potential add-ons noted):

---

1. A dispute is created in the contract (on chain).

   Can the tenderley notification here be used to pipe to the next step automatically?

2. Dispute and any indexers that can contribute to it are created in the dispute service database.

   Currently the API has you provide a list of indexer IDs. Can be modified to make a call to the network subgraph for a given dispute ID and automatically populate those IDs.

3. Indexers supply their POI through graphman CLI. Data is sent in a compressed format.

   Currently the only check here is that the indexer ID provided by the graphman CLI is contained in the dispute record that the data is being uploaded for. People could spoof their indexer id. One idea here is to use the provided POI data to validate the authenticity of this indexer. Can we get a signature from the indexer's wallet as a better guarantee?

4. When enough indexers are accounted for (TBD how to formalize this), a team mate progresses the dispute process and has the service calculate divergent blocks and save subgraph event data at those blocks.

   Progression means changing the state of the dispute in the database and making an API request for the next stage (only possible when state changes in the DB). It may be possible to determine a progression criteria to make this automated, but that ultimately sounds brittle. Would be nice to have a dispute portal frontend that allows someone to interact with these disputes and summarize them without having to connect to the database or make api calls directly.

5. Indexers dump their entities and call cache at the divergent blocks by making a request to the service, getting the block numbers, and subsequently uploading their filtered table data.

   All data is stored as csvs. Need to also verify that these are not tampered with (same concern as pt. 3).

6. All of the data is in one spot and exploratory analysis can be run. Some automated analysis can also be run (finding all mismatched entities and events)

API DOCS and Stubs

SwaggerUI available at http://localhost:8000/docs

Insomnia API request collections also in its own directory

Immediate things to do

1. GCloud secrets are required to interact with the cloud storage. What is the best way of accessing those?
2. Containerize the application
3. Make all constants environment variable configurations (.env.dev,.env.prod)
4. Get a database instance to connect to in GCS