Bump vitest 3.2.7 → 4.1.10 (1 major behind)

[pinecone-groundskeeper]

Problem

package.json pins "vitest": "^3.2.7" (locked to 3.2.7 in package-lock.json). Current published major on npm is 4.1.10 — one major ahead. This repo's vitest.config.ts only uses defineConfig from vitest/config with a basic test.include glob and environment: "node" — none of the areas vitest 4.0's breaking-changes list touches (removed 'basic' reporter, browser-mode provider API changes, removed deprecated coverage/typecheck/runner types, workspace → projects rename, dropped Node 18 support). Confirmed via npm view vitest@4.1.10 engines that vitest 4 requires Node ^20.0.0 || ^22.0.0 || >=24.0.0, which this repo's CI matrix (20.x, 22.x in .github/workflows/ci.yml) already satisfies.

Acceptance criteria

• vitest devDependency in package.json is bumped to ^4.1.10, with package-lock.json updated accordingly.
• npm test (vitest run) passes with zero failures against the existing suite in tests/ (chunk.test.ts, chunkedUpsert.test.ts, csv.test.ts, document.test.ts, env.test.ts).
• npm run typecheck still passes.

Scope

Only the vitest version bump and any resulting lockfile update. Do not change vitest.config.ts, adopt new vitest 4 features (e.g. the projects option), or touch other dependencies.

Generated by GitHub Maintenance Audit · sonnet50 · 68.9 AIC · ⌖ 5.7 AIC · ⊞ 7.9K · ◷