chore: upgrade rquickjs from 0.8 to 0.11

[rubenfiszel]

Summary

• Upgrades rquickjs from 0.8.1 to 0.11.0 (quickjs-ng engine, better performance)
• No source code changes needed — the rquickjs API is fully backward compatible
• Supersedes chore(deps): bump rquickjs from 0.8.1 to 0.11.0 in /backend #8165 (dependabot PR that was never merged)

What changed in rquickjs 0.8→0.11

• 0.9.0: Switched underlying engine from quickjs to quickjs-ng (better perf)
• 0.10.0: no_std support, PromiseHook bindings, bug fixes
• 0.11.0: Proxy object, eval filename option, iterator support

Test plan

• cargo check passes (no feature flags)
• cargo check --features quickjs passes
• cargo test --features quickjs -p windmill-jseval — 63/63 tests pass
• Backend server starts and responds on /api/version

🤖 Generated with Claude Code

[claude]

Claude finished @rubenfiszel's task in 50s —— View job

---

PR Review: Upgrade rquickjs from 0.8 to 0.11

• Gather context and review diff
• Review changes
• Post review

Verdict: Looks good ✅

This is a clean dependency version bump with no source code changes. Here's what I verified:

Changes reviewed:

• backend/Cargo.toml: rquickjs version bumped from "0.8" to "0.11", same feature flags (futures, parallel, macro) — correct and minimal.
• backend/Cargo.lock: Transitive dependency updates are all expected:
  • rquickjs, rquickjs-core, rquickjs-macro, rquickjs-sys all move from 0.8.1 → 0.11.0
  • convert_case 0.6.0 → 0.10.0 (used by rquickjs-macro)
  • relative-path 1.9.3 → 2.0.1 (used by rquickjs-core)
  • Removes duplicate proc-macro-crate v1.3.1 (consolidates to v3.4.0)
  • rquickjs-core adds hashbrown 0.16.0 dependency

No concerns found:

• No API-breaking changes — the feature flags are unchanged and no source modifications were needed
• The switch to quickjs-ng engine (happening at rquickjs 0.9) is a well-known improvement for performance
• Lock file changes are consistent with what's expected from this version bump
• No new security-sensitive dependencies introduced

Testing:
The PR description confirms cargo check, cargo check --features quickjs, and all 63 quickjs tests pass — which covers the important validation paths.

---

Reproduction / Verification Instructions

This is a backend dependency upgrade with no user-facing UI changes. To verify: ensure the Windmill backend starts correctly and any scripts using the QuickJS runtime (JavaScript evaluations in workflows) continue to execute as expected. No specific app navigation is needed — the change is transparent to end users.