chore(deps): Bump name-controller to ^6.0.1

[mcmire]

Description

There are a few notable changes between 4.2.0 and 6.0.1:

• Support for fetching proposed nicknames via Etherscan on Optimism Goerli has been removed in favor of Optimism Sepolia
• Support for fetching proposed nicknames via Etherscan on Linea Sepolia has been added
• Proposed nicknames now get automatically removed from state after 24 hours

See the changelog for more:

https://github.com/MetaMask/core/blob/%40metamask/name-controller%406.0.1/packages/name-controller/CHANGELOG.md

Related issues

Progresses #24140.

Manual testing steps

This PR should not introduce any functional changes; the petnames feature should continue to work as designed.

Screenshots/Recordings

(None)

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.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/name-controller@6.0.1	network	0	273 kB	metamaskbot

🚮 Removed packages: npm/@metamask/name-controller@4.2.0

View full report↗︎

[mikesposito]

@metamaskbot update-policies

[metamaskbot]

Policies updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.48%. Comparing base (d27a233) to head (c6a0119).
Report is 55 commits behind head on develop.

❗ Current head c6a0119 differs from pull request most recent head 6158603. Consider uploading reports for the commit 6158603 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #24229      +/-   ##
===========================================
+ Coverage    67.37%   67.48%   +0.11%     
===========================================
  Files         1278     1288      +10     
  Lines        49881    50153     +272     
  Branches     12944    13023      +79     
===========================================
+ Hits         33605    33842     +237     
- Misses       16276    16311      +35     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[metamaskbot]

Builds ready [b2070f0]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8
  • content-script: 0
  • ui: 0, 1, 10, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1967 ± 752 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	74	379	128	68	33
		domContentLoaded	10	107	25	22	11
		load	61	3866	1967	1566	752
		domInteractive	10	107	25	22	11

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 11.33 KiB (0.35%)
• ui: 0 Bytes (0.00%)
• common: -872 Bytes (-0.01%)

[metamaskbot]

Builds ready [c6a0119]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8
  • content-script: 0
  • ui: 0, 1, 10, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (977 ± 670 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	61	155	94	28	14
		domContentLoaded	9	49	15	10	5
		load	51	3492	977	1396	670
		domInteractive	9	49	15	10	5

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 11.33 KiB (0.35%)
• ui: 0 Bytes (0.00%)
• common: -872 Bytes (-0.01%)

[cryptodev-2s]

LGTM!

[Gudahtt]

There is one breaking change in this range that doesn't seem to require any changes to the extension, but I wasn't sure:

• BREAKING: Add expire limit for proposed names (#3748)

• Expired names now get removed on every call to updateProposedNames

cc @cryptotavares @OGPoyraz @vinistevam could you confirm that this change is safe to bring in?

Seems like it should be, so I will not block on this, but I wanted to call attention just in case

[Gudahtt]

LGTM!

[OGPoyraz]

Thanks for the ping @Gudahtt, as you said it's totally safe to merge it in.