[Proxy colonies M1] feat: create proxy colony via voting reputation

[bassgeta]

Description

This PR adds functionality to create a proxy colony via voting reputation.
Additionally it adds tracing between actions which are motion finalization and the motion they have finalized.
So basically

1. finalizationActionId is a new attribute set on voting reputation and multisig motions, which tells us which txHash finalized this motion.
2. finalizedActionId is a new field on the action object which tells us which txHash was finalized by this action.

So we have this bound in two ways just in case we want to search it from both ends.

Block ingestor PR

Testing

First of all, start up your dev env, run the create data script and install the voting reputation extension.
Before we try out the proxy colony part lets check out if motions are in fact linked to their finalization actions.

1. Create a mint tokens motion, fully support it and finalize it
2. Run the following queries and verify that the motion data now has a pointer to the action that finalized it

getColonyAction(
    id: "MOTION_TX_HASH"
  ) {
    id
    initiatorAddress
    finalizedActionId
    type
    motionData {
      finalizationActionId
      id
      transactionHash
      finalizationActionData {
        id
        type
        isMotionFinalization
      }
    }
  }

4. Since we see that finalizedActionData is populated and has the isMotionFinalization set to true it means we have succesfully saved this. But let's try doing it the other way around. Run the following query

listColonyActions(
    filter: {colonyId: {eq: "YOUR_COLONY_ID"}, type: {eq: MINT_TOKENS}, isMotionFinalization: {eq: true}}
  ) {
    items {
      type
      finalizedActionId
      id
      finalizedActionData {
        isMotionFinalization
        type
        id
      }
      isMotionFinalization
    }
  }

Verify that the action's finalizedActionId equals to the parent motion's txHash and that its flag isMotionFinalization is se to true. Additionally finalizedActionData should be of type MINT_TOKENS_MOTION.

1. Go to the colony dashboard
2. Create a new Manage supported chains action and choose Reputation as the decision method
   
3. Run the following query to make sure a proxy colony for this chain wasn't deployed

listProxyColonies(
    filter: {colonyAddress: {eq: "<YOUR>COLONY_ADDRESS>"}}
  ) {
    items {
      chainId
      colonyAddress
      id
      isActive
    }
  }

7. Run the following query and verify that the motion has the target chain, but no action that finalized it (Note that currently multiChainInfo is used here just to get the chain we are deploying to)

getColonyAction(
    id: "<YOUR_TX_HASH>"
  ) {
    multiChainInfo {
      completed
      targetChainId
    }
    finalizedActionId
    finalizedActionData {
      id
      multiChainInfo {
        completed
        targetChainId
        wormholeInfo {
          emitterChainId
          emitterAddress
          sequence
        }
      }
    }
  }

8. Fully support the motion and Finalize it (npm run forward-time 1 or just oppose it and get to the voting step)

9. Finalize it and verify that
a) the proxy colony was deployed by running the listProxyColonies query from above

b) the motion now has a finalizedActionId and the action multichain info is filled in

You can also check that the chain doesn't appear in the Add supported chain dropdown!

Diffs

New stuff ✨

• createProxyColonyMotion saga
• new action type ADD_PROXY_COLONY_MOTION

Changes 🏗

• The block-ingestor now tries parsing events with the proxy colony ABIs too
• Added finalizationActionId to both multisig and voting reputation motions (check out the block-ingestor)

Resolves #3450

[davecreaser]

Awesome, good stuff @bassgeta. Obviously I saw most of this done live while on the call, but I went over it again and gave it some testing locally. All working well! Aside from the one comment which you already know about (completed not being set to true in the motion action).

Checking the block ingestor PR now. On this side though all good 🚀

[davecreaser]

Would be nice to streamline this somehow so we only have to update it in one place. I'm sure you and Ioanna already thought about this though, and it's a super future improvement anyway, just throwing it out there!