refactor(1702-2): auto detect nft component

[vinnyhoward]

Description

This PR is part of a series that breaks down the original large PR #11127 into smaller, more manageable chunks.

The AutoDetectNFTSettings functionality is valuable beyond its original implementation. By converting it into a reusable component, we can:

1. Improve code maintainability
2. Reduce duplication
3. Enhance consistency across the application and ease of use

Changes

• Extracted AutoDetectNFTSettings logic from its original location SecuritySettings and into a separate component file
• Included new tests
• Updated the SecuritySettings to use the new component
• Removed related tests/constants within SecuritySettings and moved them into the new component folder

Impact

This refactored component will be used in:

• Its current original screen which is SecuritySettings
• New screens coming from the enhanced onboarding settings #1702 that is currently under progress

Related issues

Feature: #1702

Manual testing steps

1. On the wallet home screen, click on the NFTs tab and make sure they are there (use account with NFTs)
2. Goto the settings page
3. Click on Security Settings
4. Scroll down to Toggle the "Autodetect NFTs" and toggle to off
5. Check home screen under the NFT tab to make sure the enable Autodetect NFT banner is visible
6. Go back and toggle it back to on
7. Go back to the home screen wallet under NFT tabs. Make sure the banner is off

Screenshots/Recordings

Scenario 1	Scenario 2

Before

NA

After

NA

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 started on Bitrise...🔄🔄🔄

Commit hash: 2681a9b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2576f542-e407-4a81-9a3a-862bbf74b917

Note

• This comment will auto-update when build completes
• 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 started on Bitrise...🔄🔄🔄

Commit hash: 89ccef2
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/6416b678-9d2c-43f6-90c1-3bbadaa6cacd

Note

• This comment will auto-update when build completes
• 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: aa3535a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8158c7c8-4e29-4c7b-b5bf-7fe297fb8f03

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

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

[Cal-L]

LGTM