Multi Tenancy Treasury Backend Story XL

[leonieherma1]

Frontend Story: https://github.com/hypha-dao/dho-web-client/issues/463

Summary: As a DHO user I would like to see the treasury of the DHO that I am a member of.

Problem: The whole treasury is using contracts and tables, standard EOSIO, not our document graph.

Proposed solution: I believe the easiest way to make it multi-tenant compatible, and to fit into the rest of the system would be to make the treasury run on the document graph too. Migrate the data from the tables and contracts into the documents structure.

The alternative to this would be to use the DHO name - which is an EOSIO name - as scope on the tables in the existing contracts, and separate out the data this way.

Subtasks:

• [x] Get to know the contract (M)
• [x] Integrate Document Graph (S)
• [x] Prepare treasury contracts for multi-DHO - use documents for payments, attestations, redemptions. (L)

Acceptance Criteria:

• [x] Figure out how actions work - adding a redemption, etc.
• [x] Modify automated treasury scripts to use dGraph / graphQL queries to retrieve data
• [x] Support on Frontend once that is done

[leonieherma1]

@Gerard097 can i close this issue?