Allow customizing basis of route detection

[SOF3]

Description

Allow choosing pathname, query or hash to detect the route.

Checklist

• I have run cargo make pr-flow

• I have reviewed my own code

• I have added tests

[SOF3]

I am not sure how to write tests for this. Any guidance regarding how to emulate the window.location environment properly?

[teymour-aldridge]

@SOF3 You might find this section of the wasm-bindgen guide for testing in browsers useful. I would imagine that something like "open browser" -> "use appropriate function in web-sys to set route" -> "test Yew code" is probably the right way to go.

[voidpumpkin]

@SOF3 I Agree with adding another router like BrowserRouter, like HashRouter
But what do you mean by pathname or query, i think pathname translates to use of BrowserRouter all the time, and query should always be optional to hook into, after #1892 gets merged

[ranile]

I Agree with adding another router like BrowserRouter, like HashRouter

This is how this PR should be implemented. In the current state, it would be easier to re-create this PR from a fresh slate. I will leave this open though.

One more thing I would like to add: it'll be better to use gloo-history (ranile/gloo#166) crate instead of implementing HashHistory/HashLocation ourselves

[voidpumpkin]

@hamza1311 Actually im closing this since the author has not updated it for too long,
@SOF3 Feel free to ping me if you want to push new updates and need this reopened.