fix: Make QR scanner more strict

[Gudahtt]

Description

The QR scanner is now more strict about the contents it allows to be scanned. If the scanned QR code deviates at all from the supported formats, it will return "unknown" as the result (as it always has for completely unrecognized QR codes).

Previously we would accept QR codes with a recognized prefix even if the complete contents did not match our expectations, which has resulted in unexpected behavior.

Related issues

Fixes #28527

Manual testing steps

• Open the MetaMask extension and select 'Send'
• Click on the QR scanner icon in the "Send To" field and enable webcam
• Scan a ERC-20 wallet receive QR from a mobile app, which follows the EIP-681 standard and contains a valid token contract and account address
• ERC-20 Token Contract Address, which is the first address in the string, populates the "Send To" field instead of the intended recipient address

Screenshots/Recordings

Before

We didn't record this, but multiple people on the team reproduced the problem.

After

https://www.loom.com/share/be8822e872a14ec98a47547cf6198603

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
  • We don't yet have any way to test QR scanning. We will follow up later with tests, and rely on manual testing for now. Later test automation work tracked in Add QR scanner E2E tests #28528
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[metamaskbot]

Builds ready [84f9979]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (2137 ± 50 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1944	2302	2134	104	50
		domContentLoaded	1934	2271	2098	91	44
		load	1943	2293	2137	104	50
		domInteractive	29	218	62	40	19
		backgroundConnect	10	102	33	29	14
		firstReactRender	61	293	102	53	25
		getState	56	209	102	34	16
		initialActions	0	1	0	0	0
		loadScripts	1414	1752	1574	87	42
		setupStore	6	53	13	13	6
		uiStartup	2259	2832	2488	163	78

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 34 Bytes (0.00%)
• common: 0 Bytes (0.00%)

[danjm]

I manually tested on v12.6.1 and repro'd the bug, and then tested on this branch and saw the same as the above video. I also reviewed the code

[metamaskbot]

Builds ready [adc5f3c]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (2150 ± 60 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	665	2365	2066	343	165
		domContentLoaded	1882	2331	2110	117	56
		load	1921	2378	2150	125	60
		domInteractive	31	214	52	39	19
		backgroundConnect	10	119	39	30	14
		firstReactRender	63	293	112	50	24
		getState	26	150	71	31	15
		initialActions	0	0	0	0	0
		loadScripts	1398	1768	1588	97	47
		setupStore	6	59	14	15	7
		uiStartup	2170	3072	2485	208	100

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 34 Bytes (0.00%)
• common: 0 Bytes (0.00%)