fix: transaction listener for mobile

[imblue-dabadee]

Explanation

Currently, the Phishing Controller is correctly listening to the Transaction Controller's state changes and scanning the received tokens within a transaction correctly. This feature does not work correctly in the Mobile due to differences in how state changes are emitted. This fix aims to correct for that by also listening for state changes that reveal the same information.

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

---

Note

Make the transaction state change listener also handle transactions[*].simulationData patches to trigger bulk token scans; update tests and changelog.

• PhishingController:
  • Add #isSimulationDataPatch to detect transactions[*].simulationData patches.
  • Update #onTransactionControllerStateChange to extract tokens when either the whole transaction or its simulationData is patched; skip on remove and scan by chain.
• Tests (src/PhishingController.test.ts):
  • Restructure "Transaction Controller State Change Integration" suite.
  • Add case for patches on ['transactions', i, 'simulationData'] and maintain existing behaviors (no-op on remove, no tokens, default params, error handling).
• Changelog:
  • Note fix for Transaction Controller listener picking up mobile state changes.

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

[AugmentedMode]

LGTM