bug: Update zkSync Multicall3 addresses

[mds1]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

In #270, the following zkSync Multicall3 addresses were added:

• 0x47898B2C52C957663aE9AB46922dCec150a2272c for zkSync Era mainnet
• 0x89e4EDbEC85362a285d7a1D5D255ccD2b8106be2 for zkSync Era goerli testnet

Even though we can't (yet) get the standard 0xcA11bde05977b3631167028862bE2a173976CA11 address on zkSync, I thought it'd be nice if we could have the same address for both zkSync chains, so in mds1/multicall3#76 (comment) @xalexec was kind enough to redeploy Multicall3 to 0xF9cda624FBC7e059355ce98a31693d299FACd963 on both chains.

I'm going to use these as the canonical addresses in updated Multicall3 docs, so figured it'd be good to update them here too. I'm happy to PR this in tomorrow, but figured I'd open this issue as a placeholder for now / sanity check you're ok with this change.

(not technically a bug, but this felt like the right place to put this)

Expected Behavior

No response

Steps To Reproduce

No response

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

No response

Anything else?

No response