fix: Fix confirmation tx totals on layer 2 networks and for erc20 transfers

[danjm]

Description

While testing #23510, I discovered that total fees had some inaccuracies in two cases:

1. On OP layer 2 networks, the rendered total on the confirmation screen was not including the estimated layer 1 fees (as it does in the 'Estimated Fees' section)
2. For confirmations of the ERC20 transfers, the rendered total that is supposed to be ERC20 token + estimated fee was actually ERC20 token + maximum fee.

The fix for 1 was to bring in fetching of layer1 multi-network fee data into the confirmation-transaction-base component.

The fix for 2 is just to make sure that when we are rendering the transaction detail line where useMax is false, we choose the correct token fee to render (see the new primaryFee variable introduced in this PR).

These two fixes are included in separate commits

Before: Layer 2 total fees

After: Layer 2 total fees

Before: ERC20 sends

After: ERC20 sends

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.

[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 [dda2952]

• 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
  • common: 0, 1, 2, 3, 4, 5, 6
  • content-script: 0
  • contentscript: contentscript
  • disable-console: disable-console
  • policy-load: policy-load
  • sentry-install: sentry-install
  • ui: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1314 ± 443 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	68	189	121	33	16
		domContentLoaded	9	68	37	21	10
		load	56	2366	1314	923	443
		domInteractive	9	68	37	21	10

Bundle size diffs

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

[metamaskbot]

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