fix: use max in send flow

[matthewwalsh0]

Description

Fix support for the Use Max option in the send flow.

• Ensure the maxValueMode prop is populated from the Redux state.
• Skip controller state update if transaction metadata not yet added.

Also revert previous fix for the sake of minimum code.

Related issues

Fixes: #13215

Manual testing steps

See issue

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile 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]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 358e863
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c3b47da3-e11a-4a70-b67a-5fde1316a2fa

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 4a4b7cb
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/57fb3b9c-0cff-48ae-b902-9a1755392cbf

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
87.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud