chore: run lookback success and failure scans sequentially

[rabi-siddique]

closes:

• https://github.com/Agoric/agoric-private/issues/784

Description

On Arbitrum and Avalanche, trace_filter is not supported so the failed-transaction scan falls back to eth_getBlockReceipts + getTransaction (200+ CU per 10-block chunk vs 40 CU with trace_filter). Running this in parallel with the success log scan causes CU/s bursts that trigger Alchemy 429 rate-limit errors under higher transaction volume.

This PR

• Run lookback success (eth_getLogs) and failure (eth_getBlockReceipts) scans sequentially instead of in parallel in lookBackGmp and lookBackSmartWalletTx
• Skip the expensive failure scan entirely when the success scan finds a match (the common case)

Testing Considerations

• E2E testing is pending.

Upgrade Considerations

• New planner deployment for ymax0 and ymax1

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch rs-sequential-lookback

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[rabi-siddique]

Keeping it a draft until E2E testing is done.