Fix transaction status incorrectly set to dropped, submitted, or failed

[matthewwalsh0]

Explanation

Multiple fixes following the full release of the core TransactionController in the extension:

• When checking if pending transactions have been dropped in the PendingTransactionTracker, look at wallet transactions only from the current chain.
• Check if the block tracker polling should be started or stopped when the network changes, in addition to when the transaction controller state changes.
• Fix R, S, and V update to ensure zero values are recorded.
• Ignore transaction receipts with a null or invalid status.

Changelog

@metamask/transaction-controller

• FIXED: Fix dropped status detection by ignoring transactions on other chains.
• FIXED: Start polling if network changes and associated transactions are pending.
• FIXED: Record r, s, and v values even if zero.
• FIXED: Only fail transactions if receipt status is explicitly 0x0.

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 highlighted breaking changes using the "BREAKING" category above as appropriate