[HW] OneKey (QR): QR code not recognised when creating ERC20 or deploying ERC721 token

## Description
When using a OneKey hardware wallet (QR), the QR code generated by MetaMask Mobile is not recognised by the OneKey device when attempting to create an ERC20 token or deploy an ERC721 token via the Test Dapp. The signing flow cannot proceed as the device fails to scan/parse the QR code.

## Steps to Reproduce
1. Add a hardware wallet and import a OneKey (QR) account
2. Launch the Test Dapp and connect the OneKey account
3. Trigger Create ERC20 token — scan the QR code from OneKey and verify it is recognised
4. Trigger Deploy ERC721 token — scan the QR code from OneKey and verify it is recognised

## Expected Result
The OneKey device successfully recognises and parses the QR code for both the ERC20 creation and ERC721 deployment transactions, allowing the user to sign and proceed.

## Actual Result
The OneKey device does not recognise the QR code for either transaction type. The signing flow cannot be completed.

### Detection stage
Release Candidate

### Version
v8.9.0 (iOS)

### Build type
RC (Release Candidate)

### Browser
N/A (iOS app)

### Operating system
iOS

### Hardware wallet
OneKey (QR)

## Additional context
Issue affects both ERC20 creation and ERC721 deployment contract interactions, suggesting the QR code encoding for contract deployment transactions may be malformed or using an unsupported format for OneKey firmware.

## Severity
To be added after bug submission by internal support / PM.

## Media
N/A

---
*Filed via Claude bug reporter*

Start with the Test Dapp entry points for Create ERC20 token and Deploy ERC721 token, reproducing both flows with a OneKey (QR) account on iOS. Trace where each transaction produces the QR code and compare the signing inputs; done means OneKey recognises and parses both QR codes and the signing flow proceeds.

Written by the indexing model from the issue text.