Error reporting for load file differs from evaluate code

[seancorfield]

See this thread in Slack: https://clojurians.slack.com/archives/CBE668G4R/p1655749864216649

Problem:

When you load file (ctrl+alt+c enter) and that blows up with a compiler error (e.g., in a transitive namespace that is being loaded), you get a long stacktrace which can mean you need to scroll back in the output window to find the actual error. See:

https://github.com/BetterThanTomorrow/calva/blob/published/src/evaluate.ts#L442

When you perform any of the evaluate code options and that leads to a compiler error, you get the short message printed out and no stacktrace (printed) so the output is easy to read without scrolling back.

It would be better to handle error reporting for load file the same way as for evaluation, if possible (remembering the stack trace but not displaying it, I assume?).

@bpringe asked me to create this issue based on our discussion on Slack.