[helly25]

Combines the seven dependency updates that passed independently into one integration change, so their shared npm and Cargo lockfiles are validated and merged together.

AG;DR

Implementation

• Updates globals from 17.13.0 to 17.14.0 (build(deps-dev): bump globals from 17.13.0 to 17.14.0 in /extension #171).
• Updates @types/node from 26.6.5 to 26.6.6 (build(deps-dev): bump @types/node from 26.6.5 to 26.6.6 in /extension #172).
• Updates wasm-bindgen-test from 0.3.79 to 0.3.80 and its coordinated wasm-bindgen packages (build(deps): bump wasm-bindgen-test from 0.3.79 to 0.3.80 #173).
• Updates @vscode/vsce from 4.0.0 to 4.1.0 (build(deps-dev): bump @vscode/vsce from 4.0.0 to 4.1.0 in /extension #174).
• Updates globset from 0.4.20 to 0.4.21 (build(deps): bump globset from 0.4.20 to 0.4.21 #175).
• Updates eslint from 10.13.0 to 10.14.0 (build(deps-dev): bump eslint from 10.13.0 to 10.14.0 in /extension #176).
• Updates ignore from 0.4.33 to 0.4.34 (build(deps): bump ignore from 0.4.33 to 0.4.34 #177).
• Regenerates the shared npm and Cargo lockfiles once for the combined dependency set.

Reasoning

The four npm updates overlap in extension/package-lock.json, and the three Rust updates overlap in Cargo.lock. Combining the individually green updates avoids repeated lockfile conflict resolution and gives the final dependency set one authoritative integration run.

Validation

• CARGO_BUILD_JOBS=2 cargo test --workspace --locked (passed).
• npm ci --no-audit --no-fund (passed).
• npm test (66 tests passed).
• npm run compile (passed as part of npm run build).
• pre-commit run --files Cargo.lock extension/package-lock.json extension/package.json (passed).

Portability

The combined Cargo lockfile preserves the Windows dependency resolution from #177 while integrating the globset and wasm-bindgen updates. GitHub CI remains the authoritative cross-platform and VSIX validation.

Dependencies

This PR has no prerequisite PR. It supersedes #171, #172, #173, #174, #175, #176, and #177. PR #178 is intentionally excluded because its VS Code type update currently fails the engine-floor invariant and will be updated after this PR merges.

Known limitations

The local npm run build reached and passed TypeScript compilation, then could not run the WASM bundler because the host's active Homebrew Rust installation lacks the wasm32-unknown-unknown standard library. The required GitHub extension job installs that target and must pass before merge.