fix: Handle nullptr JS TypedArrays by bumping napi to 2.6.11

[Xanewok]

This fixes an instance where we roundtrip a zero-length Uint8Array in JS code and violate the slice::from_raw_parts contract (checked in debug builds at run-time since Rust 1.78) because internally napi calls it with a null pointer, see napi-rs/napi-rs#2258.

Found while running the test suite of https://github.com/ProjectOpenSea/seaport with local, most recent Hardhat+EDR.

This should unblock further testing and releasing a Hardhat version that uses the EDR-powered stack tracing.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c11ea49

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Xanewok]

These don't seem to be released in tandem (anymore?). Should we remove the comment or reword it to something like "If you bump the napi version, please also make sure that we use a compatible napi-derive"?.

This should ideally be handled by the upstream package but sometimes mistakes happen and I assume one of these were the reason for this warning, here.

[Wodann]

Feel free to. I also removed the comment in feat/multichain

[agostbiro]

The code LGTM, but there seems to be a big regression on the seaport benchmark: https://github.com/NomicFoundation/edr/actions/runs/10959402320/job/30431668868?pr=673

I reran it just in case it's a false positive.