PR Title

feat: integrate omni-search into in-app browser URL bar

Description

This PR integrates the omni-search feature (originally developed for the Explore page) into the in-app browser's URL search bar.

Motivation

• Users should have a unified search experience across the app
• The browser URL bar should leverage the same powerful search capabilities as the Explore page
• Sites should be prioritized in browser context while still providing access to tokens, perps, and predictions

Changes

1. Integrated useExploreSearch hook into UrlAutocomplete component with configurable section ordering
2. Added section order customization - Browser prioritizes Sites first, followed by filtered Recents/Favorites, then Tokens, Perps, and Predictions
3. Re-introduced Fuse.js filtering for Recents and Favorites when user types a query
4. Added proper context providers - Wrapped search content with PerpsConnectionProvider and PerpsStreamProvider
5. Reused existing components - TrendingTokenLogo and PerpsTokenLogo for consistent icon rendering
6. Fixed token navigation - Tokens now navigate to the main Asset route with proper slide-from-right animation
7. Preserved search results - Added flag-based mechanism to keep autocomplete visible when returning from token/perps/predictions detail screens

Technical Details

• Modified useExploreSearch to accept sectionsOrder option for flexible display ordering
• Added exhaustive type checking with error logging for unknown section IDs
• Updated TokenSearchResult type to include assetId for proper logo rendering
• Handled native token addresses (slip44: prefix) using NATIVE_SWAPS_TOKEN_ADDRESS

Changelog

CHANGELOG entry: Added omni-search integration to the in-app browser URL bar, allowing users to search for sites, tokens, perpetuals, and predictions directly from the browser

Related issues

Fixes:

Manual testing steps

Feature: Omni-search in browser URL bar

  Scenario: User sees empty state with Recents and Favorites
    Given the user is on the in-app browser tab
    
    When user taps the URL bar
    Then user sees "Recents" section with recent browsing history
    And user sees "Favorites" section with bookmarked sites

  Scenario: User searches and sees omni-search results
    Given the user has tapped the URL bar
    
    When user types "eth" in the search bar
    Then user sees "Sites" section first (if matching sites exist)
    And user sees filtered "Recents" matching the query
    And user sees filtered "Favorites" matching the query
    And user sees "Trending tokens" section with matching tokens
    And user sees "Perps" section with matching perpetuals
    And user sees "Predictions" section with matching predictions

  Scenario: User taps on a token result
    Given the user has searched and sees token results
    
    When user taps on a token result (e.g., "Ethereum")
    Then the token detail screen slides in from the right
    And when user navigates back, the search results are still visible

  Scenario: User taps on a perps result
    Given the user has searched and sees perps results
    
    When user taps on a perps result (e.g., "ETH-USD")
    Then the perps detail screen opens
    And when user navigates back, the search results are still visible

  Scenario: User taps on a site result
    Given the user has searched and sees site results
    
    When user taps on a site result
    Then the browser navigates to that site
    And the autocomplete closes

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Files Changed

Core Implementation

• app/components/UI/UrlAutocomplete/index.tsx - Main autocomplete component with omni-search integration
• app/components/UI/UrlAutocomplete/Result.tsx - Updated result rendering with TrendingTokenLogo and PerpsTokenLogo
• app/components/UI/UrlAutocomplete/types.ts - Added assetId to TokenSearchResult, added PerpsSearchResult and PredictionsSearchResult
• app/components/UI/UrlAutocomplete/UrlAutocomplete.constants.ts - Added BROWSER_SEARCH_SECTIONS_ORDER and TOKEN_LOGO_API_BASE_URL

Hook Modifications

• app/components/Views/TrendingView/hooks/useExploreSearch.ts - Added sectionsOrder option for flexible section ordering

Navigation

• app/components/Views/BrowserTab/BrowserTab.tsx - Updated onSelect handler for proper token navigation and search result preservation

Localization

• locales/languages/en.json - Updated autocomplete section names for consistency ("Trending tokens", "Perps")

Test Fixes

• app/components/Views/DiscoveryTab/index.test.tsx - Added assetId to mock TokenSearchResult
• app/components/Views/DiscoveryTab/DiscoveryTab.tsx - Fixed type checking for url property
• app/components/Views/TrendingView/components/ExploreSearchResults/ExploreSearchResults.test.tsx - Added sectionsOrder to mock return values