ci(rust): bump napi-derive from 3.6.9 to 3.6.11

[dependabot]

Bumps napi-derive from 3.6.9 to 3.6.11.

Release notes

Sourced from napi-derive's releases.

napi-derive-v3.6.11

Fixed

• (deps) update rust crate syn to v3 (#3407)

napi-derive-v3.6.10

Other

• update Cargo.toml dependencies

Commits

• 4694e6d chore: release (#3556)
• 023a9f0 chore(release): publish
• 0029e3d feat(cli, async-runtime): preload the threaded WASI worker pool from the load...
• 99bfe36 chore(deps): update dependency @​oxc-node/cli to v0.1.3 (#3563)
• a53f334 chore(deps): lock file maintenance (#3554)
• 1de90d7 fix(napi-derive-backend): export enum variants as writable, enumerable, confi...
• cae1c43 fix(napi): create objects with napi_define_properties on every Node version (...
• 84d890d test(async-runtime): skip the worker TLS destructor barrier check where std n...
• 252c6fa build(deps): bump fast-uri from 3.1.7 to 3.1.8 (#3557)
• 14a6ada build(deps): bump @​grpc/grpc-js from 1.14.4 to 1.14.5 (#3555)
• Additional commits viewable in compare view

[JackYPCOnline]

@strandly-the-agent safe to merge?

[strandly-the-agent]

Yes, safe to merge. Lockfile-only patch bump (napi-derive 3.6.9→3.6.11, napi-derive-backend 6.1.4→6.1.5); the only substantive upstream change is napi-derive moving its proc-macro parsing from syn 2 to syn 3, and syn 3.0.2 is already in Cargo.lock on main, so no new crate enters the tree.

What I checked

• Head 3d00f2f is on top of current main (6ea4339, the napi 3.14.1 bump), no conflicts.
• Cargo.toml pins napi-derive = "3" — stays within the declared range.
• CI on this SHA: Rust ×3 OS, Python ×15, Node.js 8/9 green, Security audit green, CodeQL neutral. One job (Node.js (macos-latest, Node 20)) was still queued when I looked — runner backlog, not a failure; the other two macOS Node jobs and all Linux/Windows Node jobs (the ones that actually exercise napi-derive) pass.
• Nothing in the 3.6.10/3.6.11 release notes touches generated binding behaviour.