feat: migrate Skeleton component (confirmations scope)

[kirillzyusko]

Description

Changelog

CHANGELOG entry:

Related issues

Fixes:

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.

[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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeConfirmations, SmokePredictions, SmokeWalletPlatform
• Selected Performance tags: None (no tests recommended)
• Risk Level: medium
• AI Confidence: 90%

click to see 🤖 AI reasoning details

E2E Test Selection:
All changed files are within the confirmations UI layer (app/components/Views/confirmations/...). These components directly impact transaction and signature confirmation flows, including send flows (from-to-row, gas-fee-details-row, network-and-origin-row, hero-row, advanced-details-row, custom-amount), token payments (pay-token-amount, pay-with-row), and general confirmation layout (footer, info-row). This makes SmokeConfirmations mandatory.

Additionally, there are changes to predict-specific confirmation UI (predict-claim-amount), which directly affects the Predictions transaction lifecycle (claiming winnings). Per tag requirements, selecting SmokePredictions also requires SmokeConfirmations and SmokeWalletPlatform because Predictions is embedded in Trending and uses on-chain confirmations.

SmokeWalletPlatform is included due to its ownership of the Trending tab (which embeds Predictions) and shared wallet activity/confirmation display integrations that could be impacted by confirmation UI changes.

No changes were made to controllers, Engine, network layer, account management, Snaps, Card, Perps, or MultiChain APIs, so those tags are not required.

Performance Test Selection:
Changes are limited to UI components within the confirmation screen without evidence of architectural, rendering-loop, list virtualization, or data-loading modifications. No Engine, controller, or heavy list components were modified. Therefore, no dedicated performance test suites are required.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
16 value mismatches detected (expected — fixture represents an existing user).
View details