Decide on the future of the HTTP stack and plan out changes

[jrozner]

We moved away from Gorilla mux to Chi after Gorilla went EOL. It's now back from the dead and we still use a few Gorilla libs (sessions, secure cookie, etc.) Go 1.22 is going to bring a proper router to the std library. We should make a decision about the router that we want to use. It might be nice to remove another dependency and move over to the std library to avoid breakage in the future or having to deal with this again if Gorilla or Chi goes EOL. There are also issues with upgrading secrecookie #1025 and gorilla session #997. After looking this this, the implementation seems really complex with the codecs. It would be nice to simplify this.

I believe right now we're using encrypted cookies to store all the session information locally. There's probably no reason we can't switch this over to server side session storage to simplify this. We may need to update the deployment scripts and docs to enable sticky sessions.

[jrozner]

#1025 and #997 were both fixed. There is probably still value in some simplification and making this choice but in the mean time we're in a good enough state.