Improve error feedback

[fntlnz]

Description:

Currently, whenever we update verdict types, the CLI receives a verdict file from the Listendev's server with a name that it does not recognize, resulting in no output and leaving users unaware of the underlying issue. The root cause seems to be related to how the CLI handles errors in such cases.

I'm opening this issue with the above in mind but the title is more generic because I believe that users should always be informed in case of errors rather than seeing no output and being left with a false sense of everything is ok.

Proposed Solution:

To address this problem and provide a better user experience, it is essential to improve the error handling in the CLI when encountering mismatched verdict file names. Rather than showing no output, the CLI should display informative error messages to users, making them aware of the issue and guiding them on how to proceed.

Suggested Approach:

1. Always show what we got (e.g: do not bail out by providing no output but at least show the output for verdicts that have been recognized
2. Inform the user about the error, and allow them a quick way to report it (e.g: open an issue)

Expected Outcome:

With the suggested changes, users encountering mismatched verdict file names will receive informative error messages, enabling them to take necessary actions and report issues to the development team if required. This improvement in error handling will enhance the overall user experience and facilitate smoother issue resolution.