Provide more detailed exception reports

[Michionlion]

In the future, we may want to handle these exceptions more explicitly, similarly to how the GatorGrader command line interface handles them. This feedback should probably be an issue for future work.

Originally posted by @Michionlion in #91 (comment)

Currently, _run_gg_check in gatorgrade/output/output.py only reports GatorGrade exception type to the user in the form of a diagnostic with the content "{command_exception.__class__}" thrown by GatorGrader. These diagnostics could be improved by catching more specific exceptions and handling each case differently, as well as referencing some included information in the exception, such as args -- the GatorGrader check arguments for some exceptions. Visit the link in the quote above for more information on how this is handled in GatorGrader itself, which should be similar to what is needed for GatorGrade.