chore: Bump gridplus-sdk to 2.7.1

[legobeat]

Description

Bump dependency gridplus-sdk to latest by lifting pin.

Related issues

• Follow-up to: fix(deps): gridplus-sdk@2.5.1->~2.6.0 #27973

Resolves

• Get a new version of eth-lattice-keyring from the gridplus team with updated version of ethereumjs/util #15927

Progresses

• Figure out if we can put the gridplus-sdk anywhere other than the background, or otherwise shrink it #15532

Manual testing steps

• Test basic GridPlus Lattic1 HW wallet flow

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]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sovpro/delimited-stream@1.1.0	None	0	7.18 kB	sovpro
npm/bitwise@2.2.1	None	0	131 kB	florianwendelborn
npm/borc@3.0.0	None	0	162 kB	achingbrain
npm/gridplus-sdk@2.7.1	environment, network	+8	2.05 MB	asmiller1989
npm/iso-url@1.2.1	None	0	13.5 kB	hugomrdias
npm/json-text-sequence@0.3.0	None	0	7.66 kB	hildjj

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/borc@3.0.0, npm/gridplus-sdk@2.7.1

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[legobeat]

@SocketSecurity ignore npm/borc@3.0.0

new author ok

[hjetpoluru]

@legobeat I was waiting for the tests to pass before providing approval and rerun failed tests. Now the tests have passed, but I see merge conflicts and there is a step failing: Socket Security: Pull Request Alerts.

[legobeat]

@SocketSecurity ignore npm/gridplus-sdk@2.7.1

network access, install script ok

[legobeat]

@hjetpoluru Thanks! It looks like it was just GH being confused with the conflict; rebased cleanly locally.

[hjetpoluru]

LGTM