feat(bridge-status): add polling for Tron same-chain swaps

[ghgoodreau]

Tron swaps use async settlement and need polling to get the destination tx hash. This is used to filter duplicate receive transactions in the activity list.

Explanation

References

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

Enables async settlement handling for Tron same-chain swaps by starting status polling and refining when polling is (re)started.

• Introduces #shouldPollHistoryItem to centralize polling decisions (polls for bridge, intent, and Tron same-chain swaps) and uses it in resume/restart polling paths
• In submitTx, detects isTronSameChainSwap, starts polling for non-EVM, and avoids immediate Completed tracking for Tron same-chain swaps (will complete via polling)
• Exports isTronChainId from bridge-controller for use in status controller
• Updates tests and snapshots to assert polling behavior for Tron swaps and adjust expected calls

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

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.