chore: restructure transactions and define CODEOWNERS

[httpJunkie]

Description

Create a transactions directory that contains code owned by the Transactions team. Focusing only on the app/components/Views directory. A follow up task could be created to tackle app/components/UI if needed.

Transaction Views

app/
  components/
    Views/
      transactions/             # (New Dir) Transactions Team Owned
        SmartTransactionStatus/ # (moved from app/components/Views/SmartTransactionStatus)

Directory Ownership in CODEOWNERS

The CODEOWNERS file is updated to include transactions views:

# Transactions Team
app/components/Views/Transactions/   @MetaMask/transactions

Implementation Plan

1. Create the new directory structure under app/components/Views/Transactions/
2. Move transaction-related Views into this structure
3. Update imports throughout codebase to reflect the new path
4. Ensure all tests pass with the new structure

Related issues

Fixes: Phase 1 for Transactions team in reorganization for Mobile codebase.

Manual testing steps

1. Ensure the application and tests run as normal. There is no functional change for this PR, only reorganization of files.

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]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 9f1e6f3
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2bff9a6e-ffd2-492a-a99b-34da833849f4

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

[httpJunkie]

I have read the CLA Document and I hereby sign the CLA

[OGPoyraz]

Confirmation changes LGTM

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 91c5e4f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/faad2522-6562-4168-8463-3d8431704c99

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 41bcf25
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/bf35b477-17c7-4bfe-8ba7-1b2f7a83f58e

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