Description

Removes legacy cancel/speed-up code and consolidates on the single CancelSpeedupModal flow. This includes dropping unused EIP-1559 modal state and deleting legacy confirmation components that are no longer used.

Motivation

• The cancel/speed-up flow now uses only CancelSpeedupModal (with useCancelSpeedupGas). The previous EIP-1559–specific modal state (speedUp1559IsOpen, cancel1559IsOpen) was never set to true and only reset to false, so it was dead code.
• Legacy confirmation components (EditGasFee1559Update, EditGasFeeLegacyUpdate, UpdateEIP1559Tx) have been superseded by the unified cancel/speed-up flow and are no longer referenced.

Changes

Legacy state cleanup

• useUnifiedTxActions: Removed speedUp1559IsOpen and cancel1559IsOpen state, their setters in open/close/error paths, and from the hook’s return value. Only speedUpIsOpen and cancelIsOpen are used with CancelSpeedupModal.
• Transactions/index.js: Removed speedUp1559IsOpen and cancel1559IsOpen from component state and from all setState calls in onSpeedUpCompleted, onCancelCompleted, and the speed-up/cancel failure handlers.
• Tests: Updated useUnifiedTxActions.test.ts, UnifiedTransactionsView.test.tsx, and Transactions/index.test.tsx to drop assertions and mocks for the removed 1559 modal state.

Legacy component removal

• Deleted app/components/Views/confirmations/legacy/components/EditGasFee1559Update/ (index, styles, types).
• Deleted app/components/Views/confirmations/legacy/components/EditGasFeeLegacyUpdate/ (component, styles, types, test, snapshot).
• Deleted app/components/Views/confirmations/legacy/components/UpdateEIP1559Tx/ (index, types).

Cancel/speed-up is now handled solely by CancelSpeedupModal in both UnifiedTransactionsView and the legacy Transactions list.

Manual: open Activity, trigger Speed up or Cancel on a pending transaction and confirm the modal and flow behave as before.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://github.com/MetaMask/mobile-planning/issues/2411

Manual testing steps

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

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.