feat: upgrade ledger keyring to fix EIP-712 issues

[Akaryatrh]

Description

Ledger team request us to upgrade the @ledgerhq/hw-app-eth to 6.42.0 to fix ledger bug for EIP-712 content
Here is some comment from Kevin LAMBERT from ledger team:
and this is original thread https://consensys.slack.com/archives/C02CYKAA8G1/p1737132760664329?thread_ts=1737106010.543919&cid=C02CYKAA8G1

⚠️ There's a difference in cherry-pick from the PR opened in front of main branch. This can be explained by the fact that #withKeyringForDevice function from metamask-controller is not part of Version-v12.11.0 branch, but exists only on main branch.

As a demonstration, here's an extract of the diff between Version-v12.11.0 and feat/upgrade-ledger-library branches (the latter being used on the PR in front of main)

-    const keyring = await this.getKeyringForDevice(HardwareDeviceNames.ledger);
-    return await keyring.attemptMakeApp();
+    return await this.#withKeyringForDevice(
+      { name: HardwareDeviceNames.ledger },
+      async (keyring) => keyring.attemptMakeApp(),
+    );

Related issues

Fixes: #29813
Please also see related PR for main branch: #29820

Manual testing steps

Will require a full regression test for ledger feature.

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension 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]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected] 🔁 npm/@metamask/[email protected]	None	+1	450 kB	metamaskbot

View full report↗︎

[Akaryatrh]

@metamaskbot update-policies

[metamaskbot]

No policy changes

[metamaskbot]

Builds ready [234571b]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

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

Page Load Metrics (1518 ± 46 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1348	1810	1521	108	52
		domContentLoaded	1339	1798	1499	97	47
		load	1378	1812	1518	95	46
		domInteractive	23	69	33	14	7
		backgroundConnect	7	52	19	15	7
		firstReactRender	14	95	28	25	12
		getState	4	60	10	15	7
		initialActions	0	0	0	0	0
		loadScripts	971	1316	1104	75	36
		setupStore	5	62	13	17	8
		uiStartup	1567	2094	1753	131	63

[dbrans]

LGTM