Fix for consistent and correctly parsed edxapp logs

[robrap]

Notes:

• Here is a search for edx-edxapp-lms Python logs showing status:info, but contain "ERROR" in the message. These are not parsing correctly.
• The edx-edxapp-lms logs have a variety of formats. Are they all from the same source? Can they be more consistent?
• What format do we want? Do we want consistency with other k8s services? Do we think [INFO] is better than INFO for searching or configuring in DD? See Fix python log parsing issues #664 (comment) for additional discussion.
• See Fix python log parsing issues #664 for a more general version of this ticket for the k8s services.
  • I don't know if any of this applies once we move to k8s.

Questions:

• Relates to the above notes:
  • Do we have incorrect status for any logs?
  • Do we care about inconsistent log formats within the LMS?
  • Do we care about consistency with k8s logs?

[robrap]

This will be challenging, as since documented in https://2u-internal.atlassian.net/wiki/spaces/ENG/pages/1277394947/Challenges+with+edx-platform+log+formatting.

[inform] @timmc-edx: As with another ticket, I will mark this as P5 and move to the containerization work. Once the initial containerization is complete, and potentially the log files have been adjusted, we can determine whether we will P4 or close this ticket.