fix: 649 search screen back and forward browsers actions reacting on typying

[qcdyx]

Summary:
Closes #649
update the URL query params only when the search action is dispatched, rather than with each character typed.

Expected behavior:
search for new york in feeds screen, click back navigation button in the browser, it goes back to the previous page instead of removing the previous keystroke.

Testing tips:

Provide tips, procedures and sample files on how to test the feature.
Testers are invited to follow the tips AND to try anything they deem relevant outside the bounds of the testing tips.

Please make sure these boxes are checked before submitting your pull request - thanks!

• Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
• Add or update any needed documentation to the repo
• Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
• Linked all relevant issues
• Include screenshot(s) showing how this pull request works and fixes the issue(s)

[github-actions]

Preview Firebase Hosting URL: https://mobility-feeds-dev--pr-660-zmzna09k.web.app

[davidgamez]

The initial search query from the home page is not set in the search query input, but the subsequence text is properly kept in it. The attached screen capture shows this.

Screen.Recording.2024-08-06.at.4.42.48.PM.mov

[Alessandro100]

If we do a search and go back it wont update the search results. This also happens with pagination.

Expected result: If we go back, the data on the page should reflect the current url

Screen.Recording.2024-08-12.at.11.21.42.mov

[qcdyx]

I forgot to mention that there's a bug where the result page doesn't change when the back navigation button is clicked. This issue also occurs on the main branch. I suggest creating a new issue to track this. @emmambd I'm currently working on the URL change and using a single state variable. @Alessandro100 @davidgamez

[davidgamez]

I forgot to mention that there's a bug where the result page doesn't change when the back navigation button is clicked. This issue also occurs on the main branch. I suggest creating a new issue to track this. @emmambd I'm currently working on the URL change and using a single state variable. @Alessandro100 @davidgamez

I checked in QA and the pagination issue is present, let's keep it outside this PR as @qcdyx suggested.

[qcdyx]

#667 @emmambd

[Alessandro100]

LGTM, intuitive way of triggering the search ✅