• fix(perps): route deposit flow to redesigned confirmations with perps header cp-7.69.0 (fix(perps): route deposit flow to redesigned confirmations with perps header cp-7.69.0 #27106)

Description

The perps deposit flow was using navigateToConfirmation({ stack: Routes.PERPS.ROOT }), which did not correctly route users to the
redesigned confirmations screen after initiating a deposit. Users could
end up on the wrong confirmation stack or without the perps-specific
header.

This change updates the flow so that when the user taps the Perps
balance token to deposit:

1. The current approval/confirmation is dismissed via handleReject()
   from useApprovalRequest.
2. depositWithConfirmation() runs to start the deposit flow.
3. On success, navigation goes to REDESIGNED_CONFIRMATIONS with
   showPerpsHeader: true instead of the previous PERPS.ROOT stack.

Dependencies on useConfirmNavigation are removed in favor of
useNavigation and useApprovalRequest so the deposit action and
post-deposit navigation are explicit and aligned with the redesigned
confirmations screen.

Changelog

CHANGELOG entry: Fixed perps deposit flow so it routes to the redesigned
confirmations screen with the perps header after a successful deposit.

Related issues

Fixes:
https://consensys.slack.com/archives/C092T3GPHQD/p1772719051867319

Manual testing steps

Feature: Perps deposit from pay-with / token list

  Scenario: user initiates perps deposit from token selector
    Given user is on a confirmation screen with "Perps balance" in the token list (e.g. perps deposit and order)
    When user taps "Perps balance" to deposit
    Then the current confirmation is dismissed, deposit flow runs, and on success the user is taken to the redesigned confirmations screen with the perps header visible

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.