Migrate to using prev and next cursor explicitly

[hojberg]

The API (with unisoncomputing/share-api#79) now supports a previous and a next cursor. Update the API integration to match.

[netlify]

✅ Deploy Preview for unison-share-ui ready!

Name	Link
🔨 Latest commit	dada6a6
🔍 Latest deploy log	https://app.netlify.com/projects/unison-share-ui/deploys/683f3d0ba0e3260008392702
😎 Deploy Preview	https://deploy-preview-82.staging.share.unison-lang.org
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 56 (🔴 down 10 from production) Accessibility: 93 (no change from production) Best Practices: 100 (🟢 up 8 from production) SEO: 75 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[ChrisPenner]

I'm not seeing anything in here that pulls the prevCursor/nextCursor from the response; or is that not in this PR?

[hojberg]

@ChrisPenner currently we don't actually use pagination on any other page than the new notification hub (which uses prevCursor and nextCursor here: #78).

The pagination added to the notification hub should be fairly easy to re-use in all these other places, but wanted to focus this PR on compatibility first (even if it isn't really in use).