chore: deploy spoke periphery and across event emitter to Monad

[bmzig]

Across event emitter: https://monadvision.com/address/0xBF75133b48b0a42AB9374027902E83C5E2949034
Periphery: https://monadvision.com/address/0xe9b0666DFfC176Df6686726CB9aaC78fD83D20d7

Due to the upgrade to openzeppelin v5, the spoke pool periphery does not have the same bytecode as the other deployed ones. Do we want to deploy off the older bytecode to have them match? Setting as do not merge until that's resolved.

[nicholaspai]

Keeping the bytecode the same will keep the address the same, right? And that's a property we want AFAIK?

[bmzig]

Keeping the bytecode the same will keep the address the same, right? And that's a property we want AFAIK?

I think the reasoning behind not keeping the same address here is that if we want to keep the same address then we need to reintroduce the openzeppelin v4 contracts and import them for the deterministic deployment contracts (as well as compile them at 0.8.23 instead of 0.8.30). The alternatives seem to either be to keep this address and redeploy the other peripheries to match the updated bytecode (or to keep this address different from the others until an update is warrented). Either way, unless we reintroduce the oz v4 contracts again and compile at 0.8.23 for some contracts, we are not going to get the same deployment addresses as what we have on other networks going forward.