feat: retrieve layer 1 gas fee from transaction controller

[OGPoyraz]

Description

This PR is aiming to implement OptimismLayer1GasFeeFlow as a first use of transactionMeta.layer1GasFee. Hence it contains removal of fetchEstimatedL1Fee function and it's helper functions.

New transaction-controller version also includes a getLayer1GasFee function which could be used to obtain layer1GasFeeValue for un-existing transactions. This is being used in swaps controller.

Optimism Layer 1 Gas Fee Flow PR in core: MetaMask/core#4055

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/1945

Manual testing steps

This PR should not affect existing gas component that shows Layer1GasFee amount which appear on send flow, confirmation page & swaps. Hence manually testing any transaction on Optimism will work fine.

Screenshots/Recordings

Before

N/A

After

N/A

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• [] I've included screenshots/recordings if applicable
• 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.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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.

[OGPoyraz]

@metamaskbot update-policies

[metamaskbot]

Policies updated

[sleepytanya]

Dev build git id, Chrome, Firefox - Optimism Layer1 Gas fees displayed in the Send flow:

[matthewwalsh0]

@metamaskbot update-policies

[metamaskbot]

Policies updated

[metamaskbot]

Builds ready [449f256]

• 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
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8
  • content-script: 0
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1319 ± 529 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	74	327	146	59	28
		domContentLoaded	16	74	34	18	8
		load	65	2464	1319	1101	529
		domInteractive	16	74	34	18	8

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 113.69 KiB (3.32%)
• ui: -1.99 KiB (-0.03%)
• common: -691 Bytes (-0.01%)

[cryptotavares]

why do we still need the getIsMultiLayerFeeNetwork selector? Couldn't we just tell if the layer1GasFee is not undefined? 🤔

[matthewwalsh0]

why do we still need the getIsMultiLayerFeeNetwork selector? Couldn't we just tell if the layer1GasFee is not undefined? 🤔

That's exactly the plan in a pending branch as it requires alot of additional changes also and test updates etc.

[sleepytanya]

Latest build - Optimism Layer1 fees displayed on confirmations screen:

[matthewwalsh0]

@metamaskbot update-policies

[metamaskbot]

Policies updated

[metamaskbot]

Builds ready [27b8937]

• 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
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8
  • content-script: 0
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1131 ± 690 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	63	427	159	88	42
		domContentLoaded	10	81	37	22	11
		load	50	3903	1131	1437	690
		domInteractive	10	80	37	22	11

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 11.35 KiB (0.33%)
• ui: -1.99 KiB (-0.03%)
• common: 9.59 KiB (0.16%)