fix: remove dependency on hashchange event

[SgtPooki]

While integrating [email protected] into ipfs-webui, I ran into an issue because ipfs-webui is using createRouteBundle from redux-bundler. In order to get the ExplorePage working properly, I had to window.dispatchEvent(new Event('hashchange')) when redux-bundler provides an updated url from the selectRouteInfo selector.

We need to decouple the hash-change event, so projects consuming these components can provide the current explore path and force updates and re-renders as appropriate. We don't want to require this property on the ExploreProvider because it would force consumers to render that provider wherever their url change logic is.

potential solutions

1. Provide a forceRefresh function in ExploreContextProps
2. Accept a url prop to ExplorePage and ensure ExploreContextProps is updated when a new url is received.
3. Ensure doExploreUserProvidedPath updates exploreState:

   ipld-explorer-components/src/providers/explore.tsx

   Lines 121 to 124 in 5c97183

   	const doExploreUserProvidedPath = (path: string): void => {
   	const hash = path != null ? `#/explore${ensureLeadingSlash(path)}` : '#/explore'
   	window.location.hash = hash
   	}

Recommended approach

• We should do item 3 above so users can call useExplore and then doExploreUserProvidedPath with whichever path
• we should not require consumers to use #/explore paths
• we should remove all hashchange listeners and window.location.path expectations.