[Hackdays 36] Search from url

[sirgalleto]

WHY are these changes introduced?

As a developer, my regular usage pattern of Polaris is:

1. Go to polaris.shopify.com
2. Wait for load
3. Type / to open the search
4. Write the search.

But it can be more efficient, and we don't need to reinvent the wheel. You can go to google.com/search?q=Shopify. In Chrome, you can even type google.com + tab and write your search directly on the bar.

This PR Implements the route https://polaris.shopify.com/search?q={searchTerm} intended to be used as a search-ready URL, now (and using the chrome site search config) the search experience can be:

1. Open a new tab
2. Write your site search shorcut ("pol" in my case)
3. Write your search.
4. Go!

Demo

Screen.Recording.2024-07-01.at.11.55.30.p.m.mov

WHAT is this pull request doing?

1. Fix a useThrottle hook's race condition that prevents the first event from being fire.

This is testable by going to polaris.com, opening the search and type one key; the result is the search non being fired

2. Create the search route

1. Create a search component exporting the same index component.
2. In the <GlobalSearch/> component, watch for the route and search term to open and fill the search.

How to 🎩

1. cd polaris.shopify.com && pnpm dev
2. Go to localhost:3000/search&q=Any Search term
3. You should see the search bar populated by default.

🎩 checklist

• Tested a snapshot
• Tested on mobile
• Tested on multiple browsers
• Tested for accessibility
• Updated the component's README.md with documentation changes
• Tophatted documentation changes in the style guide