feat: Improve Predict Across deposits for proxy setup and direct transfer flows

[pedronfigueiredo]

Explanation

This PR updates predictDeposit Across quote handling to distinguish between initial proxy setup deposits and subsequent transfer-only deposits. When the destination calldata is empty or represents a single ERC-20 transfer, the quote now skips post-swap actions and relays directly to the transfer recipient to avoid unnecessary gas and fees. When calldata is present for proxy creation and setup, the destination transactions are decoded into ordered Across post-swap actions so the proxy initialization, Safe execution, and approval flow can still run after bridging. The change preserves existing non-Predict behavior, adds focused test coverage for both Predict flows and unsupported calldata cases, and keeps the original changelog entry while adding a separate follow-up note for this improvement.

References

https://consensyssoftware.atlassian.net/browse/CONF-1043?atlOrigin=eyJpIjoiOWRmOThmZWRjZjZkNDljYTgyMTE4NTNjYWU5MzgwNDEiLCJwIjoiaiJ9

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Changes how Across quotes derive recipient and actions by decoding destination calldata (including nested batches), which can alter bridged fund recipients and post-swap execution. Risk is mitigated by extensive new unit coverage but impacts a critical transaction flow.

Overview
Across quote destination handling is overhauled to derive recipient and actions from destination calldata (preferring nestedTransactions), instead of treating predictDeposit transfers as post-swap actions.

Transfer-only destinations now send directly to the transfer recipient with no actions, while supported setup calls (e.g., createProxy, execTransaction) are decoded into ordered post-swap actions; unsupported selectors or missing required target now throw clearer errors.

Adds a new across-actions module with focused tests, expands across-quotes tests to cover transfer-only vs setup flows, batching behavior (first transfer sets recipient, later transfers become actions), and additional failure cases, and documents the behavior change in the changelog.

^{Written by Cursor Bugbot for commit 8457618. This will update automatically on new commits. Configure here.}

[matthewwalsh0]

Can we not extract this from the signature dynamically?

[matthewwalsh0]

Should this be encapsulated inside across-actions too, as it's the main entrypoint?

Get me actions for this TransactionMeta?

[matthewwalsh0]

Minor, is this the only thing that needs exporting? So ideally we only unit test this? And at the top of the file for readability?

[matthewwalsh0]

Minor, I was assuming separate functions but this works too, but maybe just getAcrossActions?

[matthewwalsh0]

Minor, what do we mean by "destination", these are just calls / functions right?

So maybe just Function not supported by Across: ${selector}?