…PredictPayWithAnyTokenInfo cp-7.73.0 (#28396)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

This PR refactors the deposit amount flow in the Predict
buy-with-any-token feature to improve correctness, reduce redundant
re-computations, and align the token amount update pattern with Perps.

**What changed:**

- **Moved `depositAmount` computation** from `usePredictBuyInfo` into
`PredictPayWithAnyTokenInfo`, co-locating the calculation with the
component that consumes it. This eliminates an unnecessary prop hop and
keeps the headless component self-contained.
- **Gated deposit amount updates on input focus** — deposit amount is
only committed when the user finishes editing (input blur), preventing
redundant effect runs and state churn while the user is actively typing.
- **Removed `isQuotesStale` logic** from `usePredictBuyConditions` —
this workaround for `TransactionPayController` timing gaps is no longer
needed, simplifying the pay fees loading derivation.
- **Added `EngineService.flushState()`** after deposit amount, token
amount, and pay token mutations to ensure immediate state consistency
for the deposit-and-order batch flow.
- **Aligned token amount callback with `amountHuman`** —
`updateTokenAmountCallback` now passes the fiat-converted `amountHuman`
from `useTransactionCustomAmount` instead of the rounded deposit amount,
matching the Perps pattern.

**Files changed (8):**

| File | Change |
| ------------------------------------- |
---------------------------------------------------------------------------------------------
|
| `PredictPayWithAnyTokenInfo.tsx` | Major — owns deposit amount
computation, input focus gating, state flush |
| `PredictPayWithAnyTokenInfo.test.tsx` | Major — new test sections for
computation, gating, dedup behavior |
| `PredictBuyWithAnyToken.tsx` | Minor — passes `currentValue`,
`preview`, `isInputFocused` instead of `depositAmount` |
| `PredictBuyWithAnyToken.test.tsx` | Minor — updated mock interface |
| `usePredictBuyInfo.ts` | Minor — removed `depositAmount` return,
removed `usePredictBalance` and `MINIMUM_BET` imports |
| `usePredictBuyInfo.test.ts` | Minor — removed `depositAmount` tests
and related mocks |
| `usePredictBuyConditions.ts` | Moderate — removed `isQuotesStale`,
simplified `isPayFeesLoading` |
| `usePredictBuyConditions.test.ts` | Moderate — removed `isQuotesStale`
tests and `getNativeTokenAddress` mock |


<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: null

## **Related issues**

Fixes: #28413

## **Manual testing steps**

```gherkin
Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]
```

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] 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](https://jsdoc.app/) format
if applicable
- [ ] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
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.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Touches Predict buy payment/deposit amount propagation into the
confirmations flow, including new state-flush behavior; mistakes could
cause incorrect amounts or extra state churn during order placement.
> 
> **Overview**
> Refactors the Predict buy-with-any-token flow so
`PredictPayWithAnyTokenInfo` owns **deposit amount calculation and
propagation** (based on `currentValue`, `preview` fees, and
`usePredictBalance`) and only commits updates when the amount input is
*not focused*.
> 
> Removes `depositAmount` from `usePredictBuyInfo` and updates the
screen/component wiring accordingly;
`updatePendingAmount`/`updateTokenAmount` now de-dupe repeated
emissions, use `amountHuman` for token updates, and call
`EngineService.flushState()` after mutating confirmation/payment state.
> 
> Simplifies pay-fee loading in `usePredictBuyConditions` by dropping
the `isQuotesStale` workaround and associated native-token normalization
logic, with tests updated/expanded to cover the new deposit gating and
rounding behavior.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
5526d80. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->