chore: update badger bridge upgrade scripts

[okjintao]

• Deploy logic + proxy bridge contracts, CurveTokenWrapper.sol contract
• Link proxy and logic contracts
• Initialize proxy contract with the arguments in the order given below*
• Update upgrade_bridge script by pasting new CurveTokenWrapper address in “NEW
  CURVETOKENWRAPPER ADDRESS HERE”
• Run upgrade_bridge.py on multisig
• Set bridge proxy contract as guest on this contract
  https://etherscan.io/address/0x1b4233242becfd8c1d517158406bf0ed19be2afe
• Have dfd approve access for new bridge proxy contract on BadgerSettPeak contract
• Have bCRVibBTC vault approve access for new bridge proxy contract

*Addresses/fees/fee splits for BadgerBridgeAdapter initializer function:
0xb65cef03b9b89f99517643226d76e286ee999e77
0xe95b56685327c9caf83c3e6f0a54b8d9708f32c4
0xe80d347df1209a76dd9d2319d62912ba98c54ddd
0x618591aa0e9a29bec84

[okjintao]

these are some of the first steps as per henry's instructions. they were done in a separate deployment before looking here.

@notbdu can you confirm that we can skip these ones i commented out?

my thinking is i only need to do two more things for the new deployed contracts (unless these old ones are correct)

• changeProxyAdmin to devProxyAdmin on current proxy
• transferOwnership to devMultisig on badger bridge adapter implementation

then someone will need to execute this script to queue the txs (myself i can do it i think?)

[notbdu]

Does the latest OZ proxy contract work with badger's dev proxy admin contract? Might be worth testing that bit in isolation as I'm not sure if they're backwards compatible across versions.

I think if we're deploying a brand new set of contracts + proxy we can remove the upgrade code.

Not sure how much is left to configure in the script below.

We'd need to update all the pointers in the config json to the newly deployed contracts and make sure the tests still run. If there are deploy things to be done, should probably do the following in fork mode:

• run this upgrade script
• run all tests while connected to new contract addrs

If tests pass, the script/deploy should be correct.

[okjintao]

CurveTokenWrapper
https://etherscan.io/address/0x11e8641b706dbe56298e7b7f54823b00f1182d70

ProxyAdmin (will be changed to dev proxy admin)
https://etherscan.io/address/0xea1573323dcd0a2ddba101eba0b0f0682b0b8b50

BadgerBridgeAdapter Logic
https://etherscan.io/address/0xfe4d003fad9c812cba6d60b07dab8977dce51f85

BadgerBridgeAdapter Proxy
https://etherscan.io/address/0xd120b381296aa255e4acd9dc80e032df2223fc6a

cc: @notbdu for the contract deployment verifications if you see anything wrong those are the ones i'm currently running with

[notbdu]

I think priority should be making sure the automated tests run against the new addrs (after running any additional setup scripts).