fix(bridge-gatsby): trigger a render on search params load

[HagerDakroury]

Package(s) involved

@amazeelabs/bridge-gatsby

Description of changes

• Added a state that get updated whenever the search params are defined, in order to trigger a render on the client

Motivation and context

A common bug on PAR that got partially fixed when using react-hook-form but wasn't completely solved expect by doing a Two pass render similar to the one implemented here. The issue is also reproducible in a new project using SLB. More on PAR issue

Some resources:

• Ongoing discussion about hydration in Gatsby
• A similar stackoverflow issue

Related Issue(s)

• PAR-1973
• PAR-1702

How has this been tested?

Manually with a new frontend project with SLB as a starter

• Before -> https://splendorous-kataifi-fda428.netlify.app/?id=2

  • First form is using useLocation directly
  • Second form is using react-hook-form. First and third field using register, second field using watch (not updated, same with getValues)

• After -> https://celebrated-sunflower-c2587c.netlify.app/?id=2

[pmelab]

Is the search enough? What about the query fragment, can we test if that works correctly?
Otherwise we maybe should store the whole url object in the state?