fix: not re-load the whole confirmation when spending cap is changed

[jpuri]

Description

Currently almost whole of confirmation page re-loads when updating spending cap. This PR makes fix to load only specific sections when spending cap is updated.

Related issues

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

Manual testing steps

1. Go to test dapp
2. Create spending cap request
3. Update spending cap - only specific section of the page should re-loas

Screenshots/Recordings

Screen.Recording.2024-12-19.at.4.39.34.PM.mov

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.

[jpuri]

Only the value above need to wait for pending to go away and not the whole component.

[metamaskbot]

Builds ready [c98aa1c]

• 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, 12, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 12, 13, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1618 ± 68 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	305	1876	1563	322	154
		domContentLoaded	1310	1865	1587	135	65
		load	1315	1879	1618	141	68
		domInteractive	21	129	36	24	11
		backgroundConnect	6	157	33	33	16
		firstReactRender	15	97	40	31	15
		getState	5	82	25	27	13
		initialActions	0	1	0	0	0
		loadScripts	969	1418	1189	109	52
		setupStore	6	81	24	26	12
		uiStartup	1519	2592	1985	266	128

Bundle size diffs

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

[jpuri]

CLosing the PR as issue is getting fixed by PR #29341