fix: cp-7.56.0 fix network enablement

[salimtb]

Description

upgrade network enablement controllers to fit with BIP-44

Changelog

CHANGELOG entry: upgrade network enablement controller

Related issues

Fixes: #19746

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​metamask/​utils@​11.7.0 ⏵ 11.8.0	+1		+1	+2
	npm/​@​metamask/​network-enablement-controller@​0.6.0 ⏵ 1.1.0	+1		+1	+1

View full report

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 4aee33a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d355256a-5fb7-42b0-8c95-9af851d4d65a

Note

• You can rerun any failed steps by opening the Bitrise build, tapping Rebuild on the upper right then Rebuild unsuccessful Workflows
• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the run-ios-e2e-smoke label on the pull request

Tip

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b4f3460
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/93c15740-6793-464a-bc1f-cb8e34881316

Note

• You can rerun any failed steps by opening the Bitrise build, tapping Rebuild on the upper right then Rebuild unsuccessful Workflows
• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the run-ios-e2e-smoke label on the pull request

Tip

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

[codecov-commenter]

Codecov Report

❌ Patch coverage is 57.14286% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.48%. Comparing base (3562734) to head (b4f3460).
⚠️ Report is 18 commits behind head on main.

Files with missing lines	Patch %	Lines
...hooks/useNetworkEnablement/useNetworkEnablement.ts	50.00%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #19734   +/-   ##
=======================================
  Coverage   76.47%   76.48%           
=======================================
  Files        3274     3275    +1     
  Lines       78928    78961   +33     
  Branches    14291    14299    +8     
=======================================
+ Hits        60364    60395   +31     
- Misses      14632    14636    +4     
+ Partials     3932     3930    -2     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[salimtb]

Broken e2e tests are not related to this PR as they also fail on another PRs, example here

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: ce207e2
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/dfa4f72a-1e22-4e10-a2a7-c876fb3589d0

Note

• You can rerun any failed steps by opening the Bitrise build, tapping Rebuild on the upper right then Rebuild unsuccessful Workflows
• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the run-ios-e2e-smoke 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
66.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[metamaskbot]

Missing release label release-7.56.0 on PR. Adding release label release-7.56.0 on PR and removing other release labels(release-7.57.0), as PR was cherry-picked in branch 7.56.0.