fix (cherry-pick):Add main frame URL property to req object whenever req is triggered from an iframe #29337

[AugmentedMode]

Chery pick PR: #29337 into V12.9.3

Description

See the attached issue in metamask planning for more details.

Related issues

Fixes:

Manual testing steps

1. Go to https://develop.d3bkcslj57l47p.amplifyapp.com/
2. Click on Proceed anyways (This phishing warning page here is expected)
3. Open the network tab to monitor network requests
4. Connect your wallet and click on a signature or transaction
5. Verify that mainFrameOrigin is included in the payload of the network request to the security alerts API

Screenshots/Recordings

Below are screenshots demonstrating the behavior of a test HTML page I created:

1. In the first screenshot, before the iframe is loaded, the console shows only the origin of the main frame.
2. In the second screenshot, after clicking the button to load an iframe pointing to example.com, the solution correctly identifies both the mainFrameOrigin (main frame) and the origin (iframe).

Before

After

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
• 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.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[metamaskbot]

Builds ready [afcab17]

• 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 (1779 ± 72 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	329	2193	1712	351	169
		domContentLoaded	1490	2134	1749	151	73
		load	1499	2151	1779	150	72
		domInteractive	26	167	54	40	19
		backgroundConnect	9	72	27	18	9
		firstReactRender	16	77	32	20	10
		getState	4	61	21	19	9
		initialActions	0	1	0	0	0
		loadScripts	1070	1630	1305	135	65
		setupStore	6	51	15	14	7
		uiStartup	1712	2384	1982	157	76