Consider moving routing closer to application code

Is your feature request related to a problem? Please describe.
From an incident, we ran into routing issues due to a hard to diagnose issue with CloudFront rewrites, and one that happened suddenly without any changes on our end.

Describe the solution you'd like
Investigate ways to move all routing to something we directly control, either back in frontend container (nginx or other) or as a router in the backend code (could bring up oauth issues). This way, we control the routing and it's not up to the whims of AWS.

The main question here is, do we want it in the backend app code, or do we want a frontend container?

One thing we have to keep in mind is how we are going to handle short url redirects and perhaps eventual products like custom domains that route back to us.

fwiw, in the interest of time and considering our few resources, I'm happy to move back to the frontend container solution and just work from there if it's easier.

Start by reading the linked incident and reviewing the current CloudFront rewrite behavior. Compare routing in the frontend container with routing in the backend, including OAuth, short URL redirects, and possible custom domains. Done means documenting a chosen direction and the scope needed to move routing under project control.