feat: Set httpOnly flag in cookie

[DafyddLlyr]

What does this PR do?

• Adds the httpOnly flag to our auth cookie
• Corresponding changes to not descructure and read the cookie in the frontend
• Some refactoring of auth methods to make things a bit easier to follow

How does auth work?

I'll move this diagram to a page in Notion as well, but this is a helpful diagram for making sense of the changes here -

sequenceDiagram
  participant Frontend as PlanX Editor
  participant API as PlanX API
  participant GoogleOAuth as Google OAuth
  participant Hasura

  Frontend ->> API: Initiate Login
  activate API
  API ->> GoogleOAuth: Proxy OAuth request

  activate GoogleOAuth
  GoogleOAuth ->> API: Redirect to callback URL
  deactivate GoogleOAuth

  API ->> API: Generate JWT

  alt Staging/Production
    API ->> Frontend: Return JWT in cookie
  else Local Dev/Pizzas
    API ->> Frontend: Return JWT in search params
    deactivate API
    Frontend ->> Frontend: Generate cookie
  end
    
    Frontend ->> API: Make request to /user/me (with cookie)
    activate API
    API ->> Hasura: Get user details
    activate Hasura
    Hasura ->> API: Return user details
    deactivate Hasura
    API ->> Frontend: Return user details
    deactivate API
    Frontend ->> Frontend: Initialise userStore

Loading

How do I test this?

• I can log into the Pizza
• I can repeatedly log in / log out of the Pizza
• I can make a request to https://api.2591.planx.pizza/user/me when logged in and I get a response (request is made via cookie)
• I can see that the Access-Control-Allow-Origin header is set to https://2591.planx.pizza when hitting /user/me as part of the auth process

(Once changes merged to staging)

• I can repeat the above steps on staging
• I can see the secure flag appended to my cookie
• I can still log in on Pizzas

[github-actions]

Removed vultr server and associated DNS entries

[DafyddLlyr]

This was the issue that was giving me so much grief (causing E2E tests to fail) - I managed to recreate on the Pizza whilst testing 🤯

I still really don't get the relationship here or what the real root cause is, but it was code for this extension in RichTextInput.tsx which was causing issues.

I'll pick up a PR to revert #2589 shortly.

[jessicamcinchak]

Thanks for getting to the bottom of this one, diagram is super helpful! Testing steps all working as expected for me, happy to test again this afternoon on staging.

[Mike-Heneghan]

Looks great! It sounds like it was a frustrating piece of work but awesome you got to the bottom of it 🥳