End to end updates to tx history logic to enable the parsing of OP_RETURN outputs and render them as part of the Transaction History tab.

• Updated useBCH.js's parseTxData function to extract the asm value from the getTxData JSON response, which is then parsed to determine whether it is an eToken tx with OP_RETURN outputs or a genuine OP_RETURN message encoded output
• The message content is then decoded into text and returned as part of parseTxData() back all the way up to Tx.js, which conditionally renders the message if it exists
• Updated mockParsedTxs.js and mockTxDataWithPassthrough.js to incorporate the new opReturnMessage parameter that is now being returned from parseTxData() in useBCH.js, as well as new message-centric mocks
• Need further discussion with @bytesofman on how best to guard against OP_RETURN outputs generated by custom nodejs scripts as they wouldn't be going through the front and backend validtion logic in Cashtab which may cause cashtab to crash if getTxData() returns an unexpected JSON response.

Deployment Order

1. Propagate T1920's null utxo fix to extension plugin
2. Land D10363
3. Then land this Diff

• arc patch D10363 to utilise the draft Send OP_RETURN message function under review
• npm start
• in-app sending of outbound OP_RETURN tx from address A to address B with normal message
• in-app sending of outbound OP_RETURN tx from address B to address A with normal message
• Force cashtab to refresh tx history instead of retrieving from local storage by sending a normal outbound tx from address A
• verify both inbound and outbound OP_RETURN messages are displayed in the Transaction History tab for both wallets and not for other non-message txs
• in-app sending of outbound OP_RETURN tx from address A to address B with blank message. Verify this is not displayed in Cashtab as D10363 ignores empty string messages
• manual sending of outbound OP_RETURN tx from address A to address B with a message containing over 150 characters (D10363 limits to 150 chars and below) and verify this is displayed appropriately by being cut off at appropriate height and width limits. This is to guard against mischievious users purposely spamming insanely long messages via nodejs to other users' tx history
• manual sending of outbound OP_RETURN tx from address A to address B with a message containing an extra long word and verify this is displayed appropriately w.r.t. word break and height clipping CSS
• send normal outbound token tx and ensure the new OP_RETURN parsing logic in useBCH.js does not break existing eToken parsing logic
• verify cross-browser compatibility in Firefox
• npm run extension
• verify OP_RETURN messages are displayed in extension mode