Include result.kore with --bug-report

[emarzion]

Fixes #2018

---

Review checklist

The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

• Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
• Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
• Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
• Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

[ttuegel]

This will only capture the output if it is being written to a file already. It will not capture the standard output. We should write the output to a temporary file first, and copy the file or print it to standard output afterward.

[ttuegel]

Because we are passing KoreExecOptions into this function now, can we extract it to the top level?