Improve Funding Round test coverage

[idiom-bytes]

Problem: Right now there are various functionalities inside DAOBot and otherwise, that could receive better test coverage. This functionality is either being tested by hand, or tests may not provide a lot of confidence.

Toward a solution: Identify test that we’re doing and what we’re not doing, to make sure we have some coverage around key items that we’ve experienced problems with.

Implement tests that takes a Funding Round going from:

• undefined -> started -> due diligence -> voting -> ended

Think of the different things that need to happen each funding round, at each stage. When starting a round:

• Creating discourse topic
• Initializing airtable rows
• Deploying tasks in github

DoD:

• Define areas that should have test coverage and prioritize providing coverage to each one of them
• Let's make sure we cover different stages in the funding process: started, due diligence, vote started...
• Let's make sure we cover different areas: funding rounds, ballots, funding distribution...

[idiom-bytes]

The requirements from this ticket overlap. Both 151 and 180 are working to provide coverage to the funding round. https://app.zenhub.com/workspaces/oceandao-60a669231c2ed7000e90684b/issues/oceanprotocol/oceandao/180