Define and estimate testbed done state

[BigLep]

Done criteria:

• The customers of this testbed work (ConsensusLab) are able to understand how they would use what we're building to accomplish their goals.
• We have all the tasks that we know for this effort listed in https://github.com/filecoin-project/eudico/issues/16
• All the tasks in the issue above have an estimate.

Why important:

• Given the goal of Eudico is to enable ConsensusLab to "engineer prototypes for their new consensus designs", we need to make sure this test effort will provide what they want. We don't want to end up in a state where we have delivered something that is different than what we were expecting. This task hopefully removes the done state ambiguity.
• Enables project planners to figure out resourcing and timelines.

Customer:

• ConsensusLab engineer(s) that will use this work
• Project planners (e.g., @BigLep , @jsoares ) who are figuring out resourcing and timelines.

Notes:

I assume this will be something like:

Implement interface X (see Y for an example)
Create a testground test like Z
...

[BigLep]

We're no longer going to do this task because:

1, Magik and Marko spoke verbally on 2021-08-11 and reviewed Magik's planned delivery and it's line line with what Marko is expecting.

2. Magik, Marko, and Alfonso will meet synchronously when Alfonso starts to do handoff, implement an example consensus algorithm toghether, and close any gaps between what was built and what is needed.
3. Magik expects to need this week and next to finish the items in https://github.com/filecoin-project/eudico/issues/16 . As a result, we're not going to estimate the individual items further.