Solara incorrectly handles search parameters

[iisakkirotko]

Expected Behavior

Any url is correctly parsed, and query parameters as well as hashes are correctly extracted

Current Behavior

If an update is pushed to Solara's router that includes both a query parameter and a hash component, such as
"/my-route?query=foo#my-section", Solara will include the hash as a part of the query parameters:

router.search = "?query=foo#my-section"

Steps to Reproduce the Problem

Call router.push(/path?query=foo#section, and print out router.search