fix: validate and sanitize vectors before sending to Qdrant

[roomote]

This PR attempts to address Issue #9266.

Problem

Qdrant was rejecting vectors containing null values with the error: "Format error in JSON body: data did not match any variant of untagged enum VectorStruct"

Solution

Added validation and sanitization in the upsertPoints method to:

• Replace null/undefined/NaN values with 0 in vectors
• Validate vector dimensions match expected size
• Log warnings when invalid values are found

Changes

• Modified src/services/code-index/vector-store/qdrant-client.ts to add vector validation
• Added comprehensive tests for the new validation logic
• Updated existing tests to properly handle vector dimensions

Testing

• Added 3 new test cases for vector validation
• All existing tests pass
• Verified that invalid values are properly sanitized

Fixes #9266

Feedback and guidance are welcome!

---

Important

Sanitize and validate vectors in upsertPoints to prevent Qdrant rejections due to null values and dimension mismatches.

• Behavior:
  • upsertPoints in qdrant-client.ts now sanitizes vectors by replacing null/undefined/NaN values with 0.
  • Validates vector dimensions in upsertPoints to match expected size, throws error if mismatched.
  • Logs warnings for invalid vector values.
• Testing:
  • Added tests in qdrant-client.spec.ts for vector sanitization and dimension validation.
  • Verified that invalid values are sanitized and dimension mismatches throw errors.
• Misc:
  • Fixes issue [BUG] Error 400 when HTTP PUT to Qdrant: Format error in JSON body: data did not match any variant of untagged enum VectorStruct #9266.

^{This description was created by for 518bc83. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Rooviewer   See task on Roo Cloud

Review completed. Found 1 issue that should be addressed:

• Console flooding: The warning in the vector sanitization map function will log once per invalid value, potentially flooding the console with hundreds of warnings for vectors with many null values. Refactor to log a single summary per point.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote]

The console.warn is called inside the map function for every invalid value. If a vector has many null/undefined/NaN values (as shown in the issue example with hundreds of nulls), this will generate one warning per invalid value, flooding the console and impacting performance. Consider collecting invalid indices first and logging a single summary warning per point (e.g., "Found N invalid values in vector for point X at indices: [...]" or "Found N invalid values in vector for point X, replaced with 0").

_{Fix it with Roo Code or mention @roomote and request a fix.}