[FEATURE] Document core EVM contracts and Cadence equivalent wrt VM Bridge

[sisyphusSmiling]

Issue to be solved

The docs are in need of documentation for commonly used EVM ecosystem contracts (WFLOW & USDC.e, Multicall, etc.), though additional contracts will likely be added over time. WFLOW & USDC.e (Celer's bridged USDC) are especially important as they require special handling by the VM bridge, the behavior for which should be documented as well.

Suggest A Solution

• A callout about FlowToken (Cadence) <> WFLOW (EVM) association and behavior when bridging
• An "Ecosystem Contracts" page under EVM with tables containing contract name & address for each contract
  • For USDC & WFLOW specifically, note the Cadence association with USDCFlow and WFLOW respectively. Caveat here is that Celer has not deploy to Testnet, so is not handled in the same manner as on Mainnet.
  • Add essential core EVM contracts such as Cadence Arch precompiles, USDC.e, WFLOW, Multicall (if needed), and any additional contracts that would be relevant.

What are you currently working on that this is blocking?

No response