fix(tempo): respect token metadata batching config

[struong]

Summary

Updates Tempo token metadata reads to honor explicit client multicall configuration while preserving deployless Multicall3 as the action's default.

Motivation

Zone clients cannot execute deployless contract-creation eth_call requests. Explicitly disabling client multicall should allow token.getMetadata to use ordinary contract reads without changing the default behavior for existing Tempo clients.

Changes

• Preserved deployless metadata multicall when the client does not specify a multicall setting.
• Used concurrent readContract calls when the client explicitly configures multicall behavior.
• Preserved pathUSD fields, declared-token overrides, logo URI fallback, and deterministic required-field errors.
• Added focused Tempo and Zone coverage plus a patch changeset.

Testing

• pnpm test src/tempo/actions/token.test.ts --run — 76 passed, 1 existing skip.
• pnpm check:types
• pnpm build:types
• Attempted VITE_TEMPO_ZONES=true pnpm test src/tempo/actions/zone.test.ts --run; the local Zone container exited before tests because the configured dev key did not own ZoneFactory.

[vercel]

@struong is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

🦋 Changeset detected

Latest commit: 5e25f5e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
viem	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/viem@4951

commit: 5e25f5e

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/viem@4951

commit: 8a41b77

[jxom]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Chef's kiss.

Reviewed commit: 5e25f5efa1

ℹ️ 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".

[struong]

Superseded by #4956, which uses a branch in wevm/viem so CI can access repository secrets.