RI-8158: vector set similarity form and table

[dantovska]

What

Builds the similarity-search UI on top of the FE foundation landed in #vector-similarity-1 (slice + thunks + useSimilaritySearch hook).

• Similarity search form (similarity-search-form/) — three self-contained components:
  • SimilaritySearchForm with vector / element mode toggle, vector or element input (with FP32 + numeric validation against the key's vectorDim), result count, filter expression, BE-built command preview, and a submit + reset action row.
  • CommandPreview — renders the BE-built VSIM preview the search would actually run, with copy-to-clipboard and a neutral placeholder while idle.
  • FilterSyntaxHelpPopover — inline help next to the filter field, listing supported operators and example expressions.
• Submit button mirrors both the search and preview loading flags so the user can't dispatch a search before the preview has settled, and stays disabled until the form maps to a valid VSIM payload.
• Reset button (IconButton to the left of "Find similar items") — clears the form's local state and dispatches the hook's resetSimilaritySearch to wipe slice state. The form also remounts on key change (key={keyName}), and the slice is cleared on key change / unmount, so the form is reset whenever the user navigates to another key, closes the key details, or otherwise leaves the view.
• Similarity search results table (similarity-search-results/) — sorted by score with a "high match" highlight (HIGH_SIMILARITY_THRESHOLD = 0.85), reusing the existing Element rendering pipeline for compressor + view-format support. Replaces the regular vector-set element list in VectorSetDetails whenever a search has results.
• Exposed bytesToBase64 and validateVector from vector-set-element-form/utils so the hook layer (from #vector-similarity-1) can build the BE payload from the form state without duplicating validation logic.
• Re-exported QuantityCounter from @redis-ui/components via uiSrc/components/base/inputs.

Testing

Light	Dark

Add vector set with elements + similarity search

Uploading Screen Recording 2026-05-08 at 14.22.07.mov…

---

Note

Medium Risk
Introduces new vector similarity-search UI and conditional rendering in VectorSetDetails, which changes user flows and relies on Redux slice/hook state; risk is mainly UI/state wiring regressions rather than security or data integrity.

Overview
Adds a vector set similarity search UI to key details: a new SimilaritySearchForm (vector/element mode, count + filter, reset, and a backend-driven command preview with copy) is rendered above the vector-set subheader.

Updates VectorSetDetails to swap the regular element list for a new SimilaritySearchResultsTable when similarity-search results exist, sorting by score and highlighting high-similarity matches.

Expands test coverage with new specs for the form, results formatting/sorting, and the details view’s conditional rendering, and re-exports QuantityCounter via the base inputs index for use in the form.

^{Reviewed by Cursor Bugbot for commit 4380b98. Bugbot is set up for automated code reviews on this repo. Configure here.}

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[github-actions]

Code Coverage - Backend unit tests

St.❔	Category	Percentage	Covered / Total
🟢	Statements	92.58%	15573/16821
🟡	Branches	74.65%	4879/6536
🟢	Functions	86.6%	2423/2798
🟢	Lines	92.41%	14884/16106

Test suite run success

3413 tests passing in 306 suites.

Report generated by 🧪jest coverage report action from 4380b98

[github-actions]

Code Coverage - Integration Tests

Status	Category	Percentage	Covered / Total
🟡	Statements	79.48%	17484/21997
🟡	Branches	61.94%	7993/12904
🟡	Functions	67.97%	2418/3557
🟡	Lines	79.04%	16441/20799

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f546a1b. Configure here.}

[github-actions]

Code Coverage - Frontend unit tests

St.❔	Category	Percentage	Covered / Total
🟢	Statements	82.74%	24446/29546
🟡	Branches	67.94%	10265/15110
🟡	Functions	77.89%	6599/8472
🟢	Lines	83.21%	23884/28705

Test suite run success

6867 tests passing in 793 suites.

Report generated by 🧪jest coverage report action from 4380b98

[valkirilov]

nit: I'm thinking of changing this to an enum, in case we use it in many places.

[valkirilov]

Do we need to fix the seeds for some reason?