[Infra] Deploy ZapPlotLink on Base mainnet + multi-token support

[realproject7]

Summary

Re-fork ZapPlotLink from MintPad's ZapUniV4MCV2 with proper multi-token fromToken support. Deploy on Base mainnet. Integrate into frontend.

Sub-tickets

1. [#432] Zap v2 Contract: Re-fork with multi-token support + mainnet deploy #433 — Contract: Re-fork with multi-token support + mainnet deploy (plotlink-contracts)
2. [#432] Zap v2 Frontend Lib: Rewrite lib/zap.ts + update constants #434 — Frontend lib: Rewrite lib/zap.ts + update constants (depends on [#432] Zap v2 Contract: Re-fork with multi-token support + mainnet deploy #433)
3. [#432] Zap v2 Frontend UI: Multi-token selector on TradingWidget #435 — Frontend UI: Multi-token selector on TradingWidget (depends on [#432] Zap v2 Frontend Lib: Rewrite lib/zap.ts + update constants #434)

Supported input tokens

• ETH (address(0)), USDC, HUNT — via Zap contract
• PLOT — direct MCV2_Bond.mint (no Zap)

Reference

• MintPad ZapUniV4MCV2: 0xa2e7BcA51A84Ed635909a8E845d5f66602742A75 (Base mainnet)
• ABI: mintpad/src/configs/abis.ts:1052-1114

[realproject7]

All sub-tickets complete. ZapPlotLinkV2 deployed on mainnet + frontend integrated. Swap-based mints blocked on Uniswap V4 pool creation (needs real $PLOT token — #31 Phase B).