Meta: Support Safe multisigs on Recall blockchain

[oed]

Context

We have a few reasons we want to enable multisig wallets on our Recall subnet:

1. A multisig that controls the "config" actor where a bunch of chain parameters are set and data can be revoked
2. A way for our users to create multisig to hold tokens and credits on our subnet

The most straight forward path is to use the most common EVM mutlisig: safe.global. However, there's one main hurdle we will need to overcome. The default Safe UI doesn't support arbitrary blockchains. There is an onboarding process, but currently they add one new chain per quarter. So we need an alternative.

One option could be to host the current Safe frontend, and associated backend, ourselves (or outsource). This is what Filecoin is doing (https://safe.filecoin.io/). However, this is really expensive to set up and operate.

The other option is the one we are going for is to use eternalsafe.eth, which is a decentralized frontend for Safe that doesn't require any backend components.

• Github: https://github.com/eternalsafe/wallet/

Through an earlier PR I was able to add custom network support to Eternal Safe. A new network can be added using normal query params.

https://eternalsafe.eth.limo?chainId=84532&chain=Base%20Sepolia&shortName=base-sepolia&rpc=https%3A%2F%2Fsepolia.base.org&currency=ETH&symbol=ETH&expAddr=https%3A%2F%2Fsepolia.basescan.org%2Faddress%2F%7B%7Baddress%7D%7D&expTx=https%3A%2F%2Fsepolia.basescan.org%2Ftx%2F%7B%7Bhash%7D%7D&l2=true&testnet=true

Below are additional issues that need to be solved in Eternal Safe for us to be able to use it fully. Additionally we need to make sure the Safe contracts can be properly deployed on our network.