Fix array query params in client-side navigation

[AshokGaire3]

What?

Replaced Object.fromEntries(new URLSearchParams(renderedSearch)) with urlSearchParamsToParsedUrlQuery when computing segment cache keys in the client-side router.

Why?

When submitting a form with multiple checkboxes that share the same name attribute, the URL reflects arrays in query parameters (e.g., ?type=test1&type=test2). During a client navigation, Object.fromEntries was incorrectly omitting all but the last parameter (resulting in {"type":"test2"}), causing the client router segment matching to falsely hit the local cache and show stale UI state.

How?

Using the urlSearchParamsToParsedUrlQuery utility correctly parses identical duplicate search parameter keys into arrays, which constructs a correct segment key, leading to a successful dynamic route prefetch on change.

Verification

• Confirmed fix with the issue reproduction script using a Playwright next start test.
• The GET request to /?type=test2&_rsc=... is correctly spawned upon navigating away from /?type=test1&type=test2.