Make Error Logging Great Again

**Describe the task**
We need to better handle error logging/messages from WFWX API

**Acceptance Criteria**
- [ ] Receiving an error message from WFWX API doesn't break our RocketChat channel
- [ ] Don't push WFWX's entire JSON file to RocketChat when there's an error
- [ ] We still receive a notification within RocketChat when an error occurs, just a condensed message
- [ ] We can view the entire error JSON in our Kibana instance

**Additional context**
- WFWX API's error JSON messages are 15,000+ lines. RocketChat can't handle that size
- Our RocketChat -dev channel is possibly broken right now - make sure that it's working again.
- Logging the error messages we receive from WFWX API will in the future be used to document the number of times we receive failures from WF1
- Our Rocketchat dev channel gets spammed with error messages on a near-daily basis and it's at the point that I just ignore them because they're so frequent. Boy Who Cried Wolf syndrome. Error messages should mean something.

No files or tests are named. Start by locating the WFWX API error-handling path, the RocketChat notification entry point, and the logging configuration used by Kibana. Done means RocketChat receives a condensed notification without breaking, while the complete error JSON remains available in Kibana.

Written by the indexing model from the issue text.