Report output limit succeeded errors

The Leetcode system has a limit on how much output (i.e. to
stdout/stderr) a problem submission can produce.  If a submission does
produce too much output (e.g. due to print statement debugging left in
by accident), Leetcode returns an error with `status_code` 13.

Currently, the `leetcode--show-submission-result` function does not
detect errors with this status code, resulting in an empty
`leetcode-result-XXX` buffer and no indication of failure.  This
change adds detection of the output limit breach and notifies the user
in the results buffer that there was a problem.  Note that we do not
list the problem that was running at the time of the error, since
that's probably not relevant to the problem of outputting to stdout et
al.

Author: dpkatz

leetcode.el

@@ -1081,6 +1081,7 @@ STATUS_CODE has following possible value:
 - 10: Accepted
 - 11: Wrong Anwser
 - 12: Memory Limit Exceeded
+- 13: Output Limit Exceeded
 - 14: Time Limit Exceeded
 - 15: Runtime Error.  full_runtime_error
 - 20: Compile Error.  full_compile_error"
@@ -1112,6 +1113,8 @@ STATUS_CODE has following possible value:
         (insert (format "Status: %s" (leetcode--add-font-lock .status_msg 'leetcode-error-face)))
         (insert (format "\n\n%s / %s testcases passed\n" .total_correct .total_testcases))
         (insert (format "Last Test Case: %s\n" .last_testcase)))
+       ((eq .status_code 13)
+        (insert (format "Status: %s" (leetcode--add-font-lock .status_msg 'leetcode-error-face))))
        ((eq .status_code 14)
         (insert (format "Status: %s" (leetcode--add-font-lock .status_msg 'leetcode-error-face)))
         (insert (format "\n\n%s / %s testcases passed\n" .total_correct .total_testcases))