Create new database for 2.0.0

[GMKrieger]

📚 Context

For the 2.0.0 release, major changes will need to be implemented to take into consideration the first part of the output unification. This effort requires a change in how the node stores data relating to the inputs, outputs and proofs

This release will also include several major changes to how the node operates, its architecture and the flow of data between the services. One such change is the deprecation of Redis, and therefore the indexer, and concentrating all the information on the database.

Both these tasks require a new database design, as well as the new GraphQL API proposed in #242 uses PostGraphile, that in on itself also is built on top of database schema.

✔️ Solution

The first step is creating the base repository, with the migrations and functions related to the basic operation of the node. This will allow other services to start being built on top of it.

Then, each service will bring forth personal needs from the database. In an effort to better divide each service's scope, most functionalities related to the database will be covered in the repository or inside the database, and the issues will be part of this epic.

A new view in a separate schema will be created for the PostGraphile.

To conclude, new tests need to be created and the previous database, indexer and GraphQL API in rust need to be deprecated.

📈 Subtasks

• Create base database migrations #347
• Implement Validator database functionalities #348
• Implement Input Reader database functionalities #349
• Create PostGraphile view in the database #368

[GMKrieger]

This epic is now obsolete, as we moved all 2.0.0 issues to #375.