Local Stack Trace Dumps

[Mesoon5642]

Title. Basically, allow for better logging of what's going on with the backend. Will need to work with Ishan, as well as figure out where to log things.

[Mesoon5642]

Ok, I made a basic version of local logging, it's pushed and live on the issue branch if you want to test it locally.

TLDR: Run npm install tslog, set the LOG_LEVEL environment variable according to the comment by the logger code, and you're off to the races. I tried to make the log format pretty easy to read.

For the deep dive, TSLog lets you feed it json and spit out another formatted json object with a lot of metadata attatched to said JSON. Rather than feed it the ENTIRE request/response body, feeding it a few attributes about each seems most prudent.

Notably, log level 6 (fatal) disables logging for the time being, log level 5 (error) only logs errors, log level 2 (debug) will log metadata about every request but will NOT log response content (only response length), and log level 1 (trace) will log the entire body of the response.

Use log level 1 sparingly and DO NOT run in production even after this feature is fully complete. It's a great way to get multi-GB log files.

Finally, I mention that this is only partially complete since I need to implement this to work on rotating log files based on timestamp, and talk to @i-kumar about how long we should be retaining log files (and if we need to write a service to manage our log files). Fun sysadmin things!

Have a good one y'all!

[Mesoon5642]

NOTE: Add logging of pathfinding output, break logs into two different .env options

[Mesoon5642]

Noting this for local specifically. We'll handle it server side in a different issue request (it's gonna require a meeting or two). @ry-lu lmk what you want in the stack trace dumps for the pathfinding algo