Add context-aware component search suggestions

[Mbeaulne]

Description

Replaces the static list of hardcoded component search suggestions with a dynamic buildComponentSearchSuggestions function that derives suggestions from the loaded component index. Suggestions are scored and ranked based on common input/output types (highest weight), registered source labels, and component name tokens, with curated fallback defaults when the index is sparse. Each suggestion now carries a kind field ("type", "source", "name", or "default") and a suggestion_position index, both of which are emitted in tracking events instead of the previous suggested_query field. Suggestions that overlap with the current query are filtered out, and the empty-state help text is updated to reflect that suggestions are derived from loaded sources.

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. Open the component search panel in the editor or dashboard with no query entered and verify that the empty-state suggestion chips reflect types and source labels from your loaded component libraries rather than always showing the same four hardcoded terms.
2. Enter a partial query (e.g. csv) and confirm that csv no longer appears as a suggestion chip.
3. Load a registered component library and verify its label appears as a suggestion chip.
4. Confirm that tracking events for suggestion clicks now include suggestion_kind and suggestion_position instead of suggested_query.
5. Run the unit tests in componentSearchSuggestions.test.ts to verify scoring, source label inclusion, and fallback behaviour.

Additional Comments

The COMPONENT_SEARCH_EMPTY_STATE_SUGGESTIONS constant has been removed. The ComponentSearchEmptyStateSuggestions component no longer sources suggestions internally; callers are now responsible for passing a suggestions prop, which allows each surface (dashboard v2 and editor v2) to supply index-aware suggestions independently.

[github-actions]

🎩 Preview

A preview build has been created at: 06-23-add_context-aware_component_search_suggestions/6da5934

[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

• Simplify component search result cards #2459
• Add context-aware component search suggestions #2458 👈 (View in Graphite)
• Add component discovery docs #2457
• Add component search analytics baseline #2456
• Limit dashboard component browse rendering #2454
• Add component search empty state suggestions #2453
• Decouple editor component search input #2452
• Polish component search explanations #2451
• Add compatible component suggestions #2450
• Add component collection search results #2449
• Add component lifecycle badges #2448
• Add component search URL state #2447
• Disable AI search when literal search finds no matches #2444
• 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
• 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.