Make the /edit permalink retrievable if the leader is logged in

[douglasnaphas]

Relates to gh-568.

[douglasnaphas]

TODO

• [x] itest: Have the leader log in, drawing on login code from v1 itest.
• [x] Don't set JWT cookies for the frontend
• [ ] Maybe save all brittle state in the URL, to deal with this nightmare? Maybe when you first get the /create-haggadah/index.html link, when you click Plan Seder after login, or maybe even when you get the home link after login, it could have your username and email in the query params. Skill issue. I had a few things in the wrong places, especially a useQuery I had forgotten about not wrapped in a QueryClientProvider, and some code in a functional component before calls to hooks.
• [x] /v2/my-seders (/v2/my-invites will be the ones I'm invited to submit libs for)
• [x] v2 seders page and rejoin flow
• [x] Use SDK v3 in v2 for /user
• [x] Make it so the leader can't enter their email address--the one from login must be used
• [ ] Don't even put the leader email address in any API calls coming from the front end
• [ ] itest: New, parallel itest. Copied from links itest. Have the leader retrieve their link from the post-login Your Seders page.
• [ ] Toughen up the passwords: larger alphabet
• [ ] Toughen up the passwords: longer length

[douglasnaphas]

Well, I think I'm going to have to re-do my whole v2 site to use Vite, or anything other than Next, because Next seems to be re-firing my backend requests periodically. I can't find a trustworthy way to disable this, or to even figure out what is going on. I think it has to do with Next's evil overwriting of global fetch. I seriously regret ever touching Next.js.

Update: It was a skill issue. I had a bunch of React things in the wrong places, especially non-hook code before hook calls at the top of a functional component.