chore: Bump lmdb

[FrederikBolding]

Bump lmdb, which errored out with a mystical error on the latest deploy. Seems like a bug and it was fixed by bumping locally 🤔

---

Note

Bumps lmdb to 2.9.4 via package.json resolutions and updates yarn.lock with new platform binaries and transitive deps.

• Dependencies:
  • lmdb: Pin to 2.9.4 in package.json resolutions.
  • Lockfile updates:
    • Platform packages: @lmdb/lmdb-* updated to 2.9.4.
    • Transitives: msgpackr (to 1.11.5), node-addon-api (to 6.1.0), node-gyp-build-optional-packages (to 5.1.1), ordered-binary (to 1.6.0), detect-libc (to 2.1.2).

^{Written by Cursor Bugbot for commit cad4386. This will update automatically on new commits. Configure here.}

[socket-security]

All alerts resolved. Learn more about Socket for GitHub.

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

Ignoring alerts on:

• [email protected]

View full report

[github-actions]

Commit cad43867929914daf6a8d629f631b5d46dd0fb68 successfully pushed to staging website:

https://metamask.github.io/snaps-directory-staging/pr/621/

[FrederikBolding]

@SocketSecurity ignore npm/[email protected]
Perhaps not the best practice, but not a security risk. Also was in the previous version that we have been using for years.