Improved interpreter error messages for quicker error identification

[Stevengre]

• When the interpreter takes a long time without producing results, I’m unsure where it is in the rewrite process and if there are any issues. Plus, after an error, I have to rerun everything from the beginning. I wrote a script to execute 1000 depth runs continuously to quickly identify problems.
• Regarding error messages like these, there’s no default saving of temporary files, so I have to rerun to find out. The stored information is in Kore, which needs to be pretty-printed to understand its meaning better. It would be great if it could be directly bound to the error messages. I feel that most issues arise from Map-related problems and incomplete coverage of conditions in function rules.

[Error] krun: .build/ukm-testing-kompiled/interpreter 
/tmp/.krun-2024-10-11-23-11-32-E5cpgVDb9R/tmp.in.RcBlduf0fG 700 
/tmp/.krun-2024-10-11-23-11-32-E5cpgVDb9R/result.kore

Debugging might be quite complex and may not allow for quick error tracking.
information: https://kframework.org/docs/ktools/"