Add compatible component suggestions

[Mbeaulne]

Description

Adds a "Compatible components" panel to the component details view that surfaces other components in the library whose input/output types are compatible with the currently selected component.

A new buildCompatibleComponentSuggestions service compares the selected component's inputs and outputs against all other loaded components. It normalizes types to lowercase, ignores Any and empty types, and handles both string and object type definitions (sorting object keys for stable comparison). Each suggestion is labelled as either "downstream" (can consume the selected component's outputs) or "upstream" (can provide inputs to the selected component), with the matched types listed. Results are capped at 6 suggestions.

The panel renders each suggestion as a clickable button that navigates to that component's detail view, showing the direction badge ("Can use outputs" / "Can provide inputs") and the matching type names.

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 library and select a component that has typed inputs or outputs.
2. Verify that a "Compatible components" section appears in the details panel.
3. Confirm that listed components show the correct direction badge ("Can use outputs" or "Can provide inputs") and matching type labels.
4. Click a suggestion and confirm the detail view navigates to that component.
5. Select a component with no typed inputs or outputs and confirm the section does not appear.

Additional Comments

Type matching is case-insensitive and Any types are excluded from matching to avoid false positives. Object types are compared by serialising their keys in sorted order.

[github-actions]

🎩 Preview

A preview build has been created at: 06-23-add_compatible_component_suggestions/1618ff9

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