Add negative constraint parsing to lexical search

[Mbeaulne]

Description

Adds support for negative constraints in lexical search queries. When a user includes phrases like "not GCS", "excluding GCS", or "without GCS" in their search, components matching those excluded terms are filtered out of the results. This allows users to express intent more naturally, such as "I want to upload a file but not to GCS", and receive only the relevant components.

This is implemented by parsing the query text before tokenization, extracting negative constraint phrases using a regex pattern, and scoring any index entry that matches a negative token as zero. The word "but" has also been added to the stop words list to avoid it interfering with scoring.

Related Issue and Pull requests

Type of Change

• Bug fix
• New feature
• Improvement
• Cleanup/Refactor
• Breaking change
• Documentation update

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Screenshots (if applicable)

Test Instructions

1. Build the search index with components that have overlapping keywords (e.g., two upload components, one for local and one for GCS).
2. Run a search query containing a negative constraint such as "upload a file but not to GCS" or "upload a file excluding GCS".
3. Verify that only the component not matching the excluded term is returned.

Additional Comments

The negative constraint pattern currently recognises the trigger words without, excluding, exclude, not, and no, optionally followed by prepositions like to, use, or using.

[github-actions]

🎩 Preview

A preview build has been created at: 06-18-parse_negative_constraints_without_not_no_exclude_/554c927

[Mbeaulne]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Debounce component search input #2433
• add client-side embeddings cached in IndexedDB #2432
• Add search quality expectation tests for lexical search #2431
• Add deep AI search to rerank all components in selected sources #2430
• Add source-diverse AI rerank candidate pool #2429
• Add negative constraint parsing to lexical search #2428 👈 (View in Graphite)
• Add fuzzy/typo-tolerant matching for component name and I/O fields #2427
• Improve component search scoring relevance #2426
• Add synonym expansion to component lexical search #2425
• Normalize component search tokens for better matching #2424
• Expand component search indexing fields #2423
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.