Spinners and client-side navigation

[LiteralGenie]

• add skeletons to card list and details pane that trigger on pagination
  • to support this, the api query was moved from the page component into a hook (ie global data instead of prop drilling)
• navigation is now done client-side using nuqs instead of nextjs / rsc magic
  • because it's not possible to update query params without a page reload in nextjs (aka shallow routing app router)
    • this meant the page would just freeze ([1a] [1b] [2]) when a pagination button is clicked, with none of the isFetching / suspense fallbacks triggering
    • even with the suggestion from here, the back button (esp when it involves url fragments) is broken
  • data for next / prev pages are prefetched now
• similarly, <Link>s to url fragments also froze the page while waiting on hydration / some rsc request ([1] [2] )
  • these were replaced by <a>s meaning these links arent registered in whatever nextjs router history when clicked. This normally breaks the back button but a popstate event listener was added to cover up this hack
  • oh and all this depends on a nextjs canary build that fixes a fragment-navigation bug but introduces a hydration error described in home-container.tsx

runs with LiteralGenie/jobber-classifier@1ffb241