docs: list Celo on the evm method pages

[viral-sangani]

Motivation

Celo is being added to mppx's known EVM chains and assets in wevm/mppx#626, following the unified evm method path per draft-evm-charge-00. This PR lists Celo alongside Base on the evm method docs.

Summary

• Added a known networks/assets table to the EVM charge page (payment-methods/evm/charge.mdx): Base, Base Sepolia, Celo (USDC + USDT), and Celo Sepolia (USDC)
• Extended the assets/chains export descriptions on the evm SDK reference pages (client and server) to mention celo/celoSepolia

All referenced exports land with wevm/mppx#626 — this PR should merge after that releases. Code samples are unchanged (no twoslash references to the new exports), so the build stays green against the currently published mppx.

Asset metadata behind the new entries was verified on-chain (addresses from Circle's/Tether's official deployments; EIP-712 domains recomputed against on-chain DOMAIN_SEPARATOR(), EIP-3009 probed functionally on both tokens).

🤖 Generated with Claude Code

[vercel]

@viral-sangani is attempting to deploy a commit to the Tempo Team on Vercel.

A member of the Team first needs to authorize it.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 79861f25ec

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Don't publish unreleased Celo asset exports

If this docs change is merged before the corresponding mppx release, this table sends users to evm.assets.celo.* exports that the docs site's pinned SDK dependency doesn't provide yet (package.json/pnpm-lock.yaml are still on mppx 0.8.1, and the Celo exports are only in the referenced upstream PR). Users following the page before that release get compile/runtime failures when they copy these identifiers; either gate this text until the SDK release is available or update the dependency lock alongside it.

Useful? React with 👍 / 👎.