feat: add emergency treasury initialization and recover funds function

[taayyohh]

After a successful proposal from BuilderDAO to SelloutDAO -- this transaction was executed: https://nouns.build/dao/base/0xe8af882f2f5c79580230710ac0e2344070099432/vote/15

The issue is, because BuilderDAO is now on BASE, and nouns.build allows users to create DAOs on multiple L2s, the shortcuts that compose proposal arguments (in this case Transfer), do not take into account the possibility of cross chain interactions.

So the funds were sent to the address of our treasury on BASE instead of the address of our treasury on Zora Network.

Using CREATE2, the Manager contract is able to deploy the Treasury contract on Base with the same address that it exists on Zora, however there are 2 issues

1. The Treasury must be initialized by the Manager contract (setting the owner of the treasury contract)
2. The Treasury contract can only interact with funds through proposals (this is a good thing)

To recover the funds on BASE I am proposing to make these temporary changes to the protocol that allow the owner of Manager to initialize a treasury using CREATE2, and then allow the owner of a treasury (which is the governor contract for all existing DAOs) to withdraw the funds to an arbitrary address

I believe this should not introduce any security concerns for existing DAOs, but would also allow the multisig that controls Builder to help Sellout DAO recover these funds

Steps to Recovery

1. changes to Treasury and Manager contracts in my open PR are approved and merged in
2. new implementation of Treasury contract is deployed
3. new implementation of Treasury is registered as an upgrade
4. new implementation of Manager is deployed
5. manager is upgraded to this implementation
6. multisig calls function to deployAndInitializeTreasury with the given args to determinsticaly deploy to the treasury address that exists on Zora, but we do so on Base (making my EOA the owner of this treasury)
7. my EOA is now owner of initialized treasury, I upgrade treasury to the newly registered upgrade
8. I call recoverFunds on treasury to send funds to my EOA, bridge to Zora, deposit in my DAOs treasury
   CLEANUP
9. change Manager implementation back to previous implementation