feat(ramp): add activation keys labels and DS components

[wachunei]

Note

Supersedes #8549

Description

This PR changes the components used in the Settings views of Buy & Sell and adds a label property to the activation keys (not used in production).

Related issues

Fixes #8022
Closes #8549
Fixes https://consensyssoftware.atlassian.net/browse/RAMPS-1490

Manual testing steps

1. Go to Settings (Development or Ramp UAT build)
2. Go to Buy and Sell Crypto
3. Add Activation Key
4. Edit Activation Key

Screenshots/Recordings

Before

before_activation_keys.mp4

After

after_activation_keys.mp4

Pre-merge author checklist

• I’ve followed MetaMask 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]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: f77bd5c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ef56f4ae-3bed-4b2f-9ab5-ae167cc0856c

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 89914af
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5dec6625-9e14-495d-bbb4-744b1d5bf621

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[brianacnguyen]

just a small change requested regarding imports

[tommasini]

LGTM!
Small nit, it makes sense to keep two components under Settings folder on Ramps folder?

[wachunei]

@tommasini @brianacnguyen I had to solve conflicts manually and reviews went stale, would you mind re-approving please 🙏

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 441c051
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/458de876-c426-4619-b453-da229c1acb08

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 0ed4954
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e043f7c6-d699-470c-9974-5c2cee0270dd

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[wachunei]

@desi please let us know if the translations can make it for today, otherwise we can merge this and bring them in later as agreed yesterday.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud