Request URLs with UTF-8 characters in them failing to be logged for analytics

[GUI]

Due to the semi-recent changes in how we gather the logs for analytics processing, URLs containing UTF-8 characters were failing to be properly logged. So, for example, if you had a URL containing "?utf8=✓", the request would work just fine, but our background processing to log that in our analytics db was failing. This was due to how nginx escapes and logs special characters.

Surprisingly, this hasn't actually affect much of our traffic. It's only been cropping up in our error logs a few times a day, but it's still definitely something we want to fix.

[GUI]

Fixed by NREL/api-umbrella-router@673ca14 I've added tests to ensure that a variety of weird URL encodings get logged properly. And while there weren't any issues with proxying these URLs containing utf8 characters, I've also added additional sanity check tests just to verify that.