refactor(ramp): show Ramp settings logout toasts via ToastService

[wachunei]

Description

Ramp design-system migration phase 3 (toast) for in-scope Views: SettingsModal no longer reads ToastContext from the component library. Logout success and error notifications now call ToastService.showToast, which uses the same toast ref registered by Root’s ToastContextWrapper (same path as v2OrderToast).

Toast payloads still use the legacy component-library ToastVariants and icon options because the mounted app toast remains the legacy implementation; this change removes context coupling from the modal and aligns tests with ToastService mocks.

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: Ramp Transak settings — logout toast

  Scenario: Successful logout shows success toast
    Given the user is on the Ramp flow with Transak as provider and is authenticated
    When the user opens Ramp settings and taps Log out
    Then a success toast is shown with the logged-out message

  Scenario: Failed logout shows error toast
    Given the same authenticated Transak context and logout will fail (e.g. forced error in dev)
    When the user taps Log out from Ramp settings
    Then an error toast is shown with the logout error message

Screenshots/Recordings

Before

N/A

After

N/A

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - draft PR

All E2E tests pre-selected.

View GitHub Actions results

[github-actions]

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[wachunei]

I will close this PR since the current approach is not deprecated