feat(ramps): poll neo-bank deposits and emit status notifications

[saustrie-consensys]

Explanation

Part of the MM Neobank MVP0 (Brazil 🇧🇷) onramp flow. When a user funds a Money Account via Pix, the partner (Iron) pays out mUSD on Monad, and Core needs to notice those deposits so the app can react.

This adds emit-only deposit polling to RampsController (TRAM-3898, "poll for deposit and notifications"). The vault "sweep" (the original step 3) was removed from the ticket, so this PR only detects and reports: it takes no on-chain action, and vault sweeping stays with the backend.

How it works, reusing the autoramp/order patterns already in this package:

• NeoBankService.getAutorampTransactions(autorampId) fetches a partner's deposit/transaction records, mapped via the exported mapNeoBankTransactionToRemoteSnapshot (accepts a bare array or a { transactions } envelope; rejects items missing id/status).
• moneyAccountDeposit.ts is a thin local clone model mirroring autorampAccount.ts: a status enum plus a pure applyDepositRemoteStatus diff returning statusChanged / shouldNotify.
• A sibling poll loop (startDepositPolling / stopDepositPolling, plus refreshDeposits for app-load catch-up) reuses the order poller's 30s interval and error backoff. Each cycle upserts a persisted state.deposits array and publishes RampsController:depositStatusChanged on status transitions. Only Approved autoramps (or ones with an in-flight local deposit) are polled, so an in-flight deposit keeps being tracked even if its route later goes terminal.
• markDepositAsNotified dedupes repeat notifications for the same status; removeDeposit lets consumers prune the persisted list.

The client tracks the real MoonPay/Iron AutorampTransaction that the neobank-proxy (onramp-api PR #1124) forwards verbatim: GET /neobank/autoramp-transactions?autoramp_id={id}, returning an Iron PagedList (items array) with the payout hash nested at payout_crypto_transaction.transaction_hash, and the 8 AutorampTransactionStatus values. Because #1124 is unmerged and its own fixtures use a transitional data / flat transaction_hash shape, the mapper reads both envelopes (items then data then a bare array) and both hash locations (nested then flat) so it works whichever ships. Still mocked in unit tests until #1124 merges. Deferred to the mobile-safe DTO in TRAM-3925 (unstarted): the display field names (amount / currency / money-account, which MoonPay carries as structured objects), and cursor pagination — the poll reads the first page only for now.

Known behaviors worth a reviewer's eye

• A deposit first observed already in a terminal state (app closed across the whole in-progress-to-terminal window) is recorded for display but fires no depositStatusChanged notification (there is no prior local state to have transitioned from). Whether catch-up should toast is a product question.
• Unknown / renamed partner statuses fall back to a non-terminal in-progress value (FundsReviewInProgress), so an unrecognized status keeps polling rather than being mistaken for a terminal outcome — best-effort until TRAM-3925 pins the wire values.
• state.deposits is a live mirror of the proxy for actively-polled (Approved) autoramps, so it grows with the user's deposit history. removeDeposit prunes local state, but a deposit under a still-polled autoramp re-syncs on the next poll (it only sticks once the autoramp is no longer pollable).

Hosts must delegate NeoBankService:getAutorampTransactions (added to RAMPS_CONTROLLER_REQUIRED_SERVICE_ACTIONS), or startDepositPolling / refreshDeposits reject with a messenger "handler has not been delegated" error.

References

• Refs: TRAM-3898
• Depends on the NeoBankService + autoramp work already merged to main (feat(ramps-controller): add NeoBankService and wallet registration HTTP client #10031, feat(ramps-controller): autoramp controller methods and last-seen functionality #10032).
• Proxy endpoint: onramp-api Support watching assets on a specific account #1124 (GET /neobank/autoramp-transactions, Matt Ilagan) — not yet merged; mocked here.
• Response DTO / field names: TRAM-3925 (mobile-safe NeoBank proxy responses, unstarted) may rename the display fields.
• Related: feat(ramps): add RampsController sendPix orchestration #9856 (RampsController:sendPix, the opposite direction).
• Mobile consumers: toast TRAM-3901, account screen TRAM-3887 / TRAM-3889, hydrate-on-load TRAM-3900.
• Supersedes feat(ramps): poll neo-bank deposits and emit status notifications #10108 (that draft was mistakenly stacked on the stale hackathon branch feat(ramps): add NeoBankService Pix and quote client methods #9851; this one is based on main).

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