fix: Gas changes for low Max base fee and Priority fee

[pedronfigueiredo]

Description

Previously, if the Max base fee and Priority fee were reduced to very low values, the Network fee wouldn't update accordingly. This is a discrepancy with the gas calculations in the old flows.

What fixes it is, for low enough values of maxFeePerGas (low enough to be lower than minimumFeePerGas), the Network fee becomes the Max fee -- maxFeePerGas times gasLimit directly. Apart from fixing the symptom explained above, this ensures that the Network fee is never higher than the Max fee.

The PR also fixes this calculation when it comes to the L2 fees (inside useTransactionGasFeeEstimate).

It also adds a missing override of dappSuggestedFees for both maxFeePerGas and maxPriorityFeePerGas (inside useEIP1559TxFees).

Related issues

Fixes: #27802

Manual testing steps

See original report above.

Screenshots/Recordings

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 [40b0571]

• 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, 10, 11, 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 (1934 ± 76 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1685	2514	1933	163	78
		domContentLoaded	1670	2489	1904	159	77
		load	1733	2508	1934	157	76
		domInteractive	23	98	45	21	10
		backgroundConnect	13	69	28	18	9
		firstReactRender	48	158	92	25	12
		getState	5	75	20	21	10
		initialActions	0	1	0	0	0
		loadScripts	1204	1990	1416	151	72
		setupStore	12	69	30	22	11
		uiStartup	1896	2690	2138	156	75

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 733 Bytes (0.01%)
• common: 0 Bytes (0.00%)

[metamaskbot]

Missing release label release-12.6.0 on PR. Adding release label release-12.6.0 on PR and removing other release labels(release-12.7.0), as PR was cherry-picked in branch 12.6.0.