Add component search URL state

[Mbeaulne]

Description

The component search state (q and disabled_sources) is now persisted in the URL, making searches shareable and preserving state across page refreshes. A "Copy component link" button has been added to the detail pane so users can copy a URL that includes the selected component, active search query, and source filters.

Key behaviors:

• The search input initializes from the q URL param on mount and syncs back to the URL after a debounce, without trimming whitespace while the input is focused.
• Focused input is protected from URL echo updates — navigating back to the same page with a slightly different URL (e.g. trimmed query) will not overwrite what the user is actively typing.
• Source filter toggles immediately write disabled_sources into the URL.
• Closing the detail pane preserves the active search query and source filters rather than clearing all search params.
• useDebouncedSearchValue now accepts an initialValue and a shouldSyncExternalValue guard so external value changes can be blocked while the input is focused.
• New helpers readComponentSearchQuery, readDisabledSourceKeys, and createDashboardComponentsV2SearchParams centralize URL param parsing and serialization, with unknown source keys silently dropped.

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. Navigate to the Components V2 dashboard page.
2. Type a search query and verify the q param appears in the URL after the debounce delay.
3. Reload the page and confirm the search input and filtered results are restored from the URL.
4. Toggle source filters and confirm disabled_sources updates in the URL immediately.
5. Open a component detail pane, then close it and confirm the search query and source filters remain in the URL.
6. With a component selected, click "Copy component link" and paste the URL — confirm it includes the selected component, query, and filters.
7. Type in the search input rapidly and confirm the URL does not rewrite the input value while it is focused.

Additional Comments

The disabled_sources param only accepts the known source keys (standard, published, registered, user); unrecognized values are silently dropped during parsing and serialization.

[github-actions]

🎩 Preview

A preview build has been created at: 06-23-add_component_search_url_state/1e0f470

[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
• Add component lifecycle badges #2448
• Add component search URL state #2447 👈 (View in Graphite)
• 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.