IRO-1307 - Address UI lag in rendering Magic Link state

[brekk]

• Remove LoginContext usage
• Number explicit error boundaries
• thread props for loginContext, coming from pages/_app directly. This ends up being both more reliable and ultimately more readable / easier to reason about.
• refactor to use useRouter instead of Router.push

[linear]

IRO-1307 Figure out why the page renders before the magic link data hooks

Our Toast says 'welcome back' but the other parts of the UI don't know you're logged in until a refresh. It's lame.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/ironfish/website-testnet/CVXhyaV2mc8EXw4tnmDWSCMiG46S
✅ Preview: https://website-testnet-git-feature-iro-1307-magic-link-7bcac1-ironfish.vercel.app

[dguenther]

This doesn't work as expected. When logging out, after the redirect happens, the Login page appear to be logged out, but if you click on Leaderboard, the navbar appears to be logged in again.

The source of the issue is the multiple instances of useLogin created by useProtectedRoute. The site only needs one source of truth for whether the user is logged in or not, so we can centralize that in the single useLogin in _app.tsx. useLogin should either contain all of the auth logic and export functions to control it, or export functions to control its state so that e.g. logout can clear the state and the login callback can update or trigger a reload of the state.

The use of Context is irrelevant to fixing this issue, but I'm not opposed to prop-drilling since there aren't too many components in the component tree anyway.

[brekk]

The source of the issue is the multiple instances of useLogin created by useProtectedRoute.

Yeah, you're right. I'm not sure when I made that mistake but that's correct. Will try to address this morning.