Determine how to get logs parsed correctly in DD

[robrap]

Some Python logs are not being parsed correctly in DD. This ticket is for discovering the right approach to fixing, and potentially to implement the fix. Not sure what rollout to all services would look like.

See https://twou.slack.com/archives/C06DMDFNBJQ/p1716412193153829 for details. This is around getting INFO logs to be recognized as INFO, and ERROR logs to be recognized as ERROR.

• SRE proposed updating the log format from the service to be more consistent and match DD's default expectations.
• I had created https://2u-internal.atlassian.net/browse/GSRE-1748, because this seems like a case where the log format is as expected, but it still isn't being parsed correctly by DD.

Note that status:info AND "ERROR" are one class of issues, and status:error AND "INFO" are a different class. WARNING is yet another case that should ultimately work.

Note: This may also affect multi-line log parsing, and whether stack traces are parsed correctly.

[robrap]

This is a duplicate of https://github.com/edx/edx-arch-experiments/issues/664. Closing this duplicate.