Add component collection search results

[Mbeaulne]

Description

When a user searches for components, registered library collections whose labels match the query are now surfaced as a distinct "Collections" section above the individual component results. Each collection card displays the library name, a component count badge, and a preview of up to three component names.

The buildComponentCollectionMatches function groups matching index entries by their registered source ID, filters by label against the search query, and sorts results alphabetically. Collection results respect the active source filter — if the "Registered libraries" source is disabled, collection cards are hidden. The "no results" empty state is also updated to account for collection matches, so it only appears when both component and collection results are empty. The result count label was updated from "results" to "component results" to distinguish it from collection results.

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 components dashboard.
2. Type a query that matches a registered library label (e.g. "github").
3. Verify a "Collections" section appears above the component results, showing the matching library name, component count, and a preview of component names.
4. Disable the "Registered libraries" source filter and repeat the search — confirm the collection card no longer appears.
5. Search for a term with no matches and confirm the "No components matched" message still appears.

Additional Comments

[github-actions]

🎩 Preview

A preview build has been created at: 06-23-add_component_collection_search_results/3a8d3ed

[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
• 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 👈 (View in Graphite)
• 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.