Fails are now logged

[AarjavJain101]

Purpose of Change:

• Allows quick viewing of what parse fails occurred in there verbose format for better understanding. Although the parse fail is printed when link_telemetry is running, if there is a flurry of messages finding the parse fails is bother some. Instead catting the session of parse fails is much easier. Session meaning each time link_telemetry is ran. For example, when running a full integration CAN test and parse fails occurred because of a missing message in the DBC, scrolling through terminal is not ideal. Instead, typing cat dbgfiles/<NAME_OF_LATEST_FILE> is much more efficient to see what actually went wrong in its verbose format.

Changes:

• Added another call to write_to_log_file after the calls to log the raw message during a PARSE FAIL or a INFLUX WRITE FAIL that logs the exact colorful debug message you see in the terminal
• Changed logging function option to convert message to hex numbers or not (to preserve original colorful parse fail debug message)
• Added appropriate global variables for the DEBUG_DIRECTORY and the DEBUG_FILE_NAME. This code mimicked the existing one for the LOG_DIRECTORY and LOG_FILE_NAME.

Testing:

• Tested with setting a non-existent CAN ID in the can message randomizer function and ran with the randomizer to force parse fails. Then I confirmed by catting the log file in the dbgfiles folder and received the pretty printed debug message.

[mjohal67]

Approved.