feat: add cursor pagination in recon engine transformed entries

[susrithasabbini]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Reworks the Recon Engine → Transformed Entries screen to use the cursor-paginated V2 API and adds field-specific search, rule tabs, and server-side date sorting.

Motivation and Context

How did you test it?

Locally

Where to test it?

• INTEG
• SANDBOX
• PROD

Backend Dependency

• Yes
• No

Depends on the recon-engine POST /staging_entries/v2/list cursor endpoint (juspay/hyperswitch-recon), including the microsecond-precision cursor fix described above.

Backend PR URL:

Feature Flag

• New feature flag added
• Existing feature flag updated
• No feature flag changes

Feature flag name(s):

Checklist

• I ran npm run re:build
• I reviewed submitted code
• I added unit tests for my changes where possible

🤖 Generated with Claude Code

[semanticdiff-com]

Review changes with  

[XyneSpaces]

[should-fix] fetchAccounts in src/ReconEngine/ReconEngineScreens/ReconEngineData/ReconEngineDataTransformedEntries/ReconEngineDataTransformedEntries.res silently swallows account-fetch failures (catch { | _ => () }). If the accounts list call fails, the filter dropdown stays empty and the user gets no error indication.

Surface the failure through screenState or at least log it, instead of discarding the exception.

let fetchAccounts = async () => {
  try {
    let accounts = await getAccounts()
    setAccountData(_ => accounts)
  } catch {
  | err =>
    Console.error2("Failed to fetch accounts: ", err)
    setScreenState(_ => PageLoaderWrapper.Error("Failed to fetch accounts"))
  }
}