JBP-536: V5 Ops Cleanup

Synopsis

https://jango.eth.sucks/32736EB3-2906-45AC-8887-3A328355799C/

With the deployment of the V5 protocol (see the post above for context), Juicebox DAO has a few back office todos to get things cleaned up:

- Formalize our new JBDAO omnichain multisig (0x80a8F7a4bD75b539CE26937016Df607fdC9ABeb5), with which we deployed V5. Right now this is a 2 of 5 multisig that allows 0xBa5ed and I to operate without coordinating a larger crew. We should move our V4 $NANA revnet to be operated by this new multisig.

- Our current multisig (dao.jbx.eth) should set ENS record omnichain.dao.jbx.eth to point to this new multisig.

- Allow this new multisig to set the metadata for V4 $NANA (https://app.revnet.eth.sucks/eth:1\) to make clear that it is deprecated and that funders should allocate to V5 $NANA (https://app.revnet.eth.sucks/v5:eth:1\). See the changes we've already made to V4 $CPN, $REV, and $BAN (https://app.revnet.eth.sucks/eth:2\, https://app.revnet.eth.sucks/eth:3\, https://app.revnet.eth.sucks/eth:4\)

- Cash out our positions from V4 $NANA (omnichain.dao.jbx.eth), $REV (dao.jbx.eth), and $BAN (dao.jbx.eth), symbolizing our intent to no longer focus on growing these revnets. Pay these reclaimed funds from cashing out into the V5 revnets. Allow others holders to join in on this cash out such that the cash out tax is shared between all who wish to participate. Allow Jango to coordinate this procedure.

Specification

The specification is listed above. The DAO should trust the executive direction of Jango and 0xBa5ed's consensus when scheduling these transactions. The goal here is to expedite a transition to V5 while cleaning up and tying up loose ends as we do it, with minimal bureaucracy.