fix: Mention exception in log message on failures

[runeflobakk]

Brief, plain english overview of your changes here

A small suggestion for some improved ergonomics when reading log output from db-scheduler in the case of failures.

I always find it effective to include a small "summary" of any caught exception in the actual log message. Often this will allow me to pinpoint the error at hand without needing to look into the stacktrace of the logger event. (But this is still possible of course, as before)

Logs when exceptions propagates all the way back to db-scheduler can typically look like this:

This PR will change the log message to mention the actual exception which was caught in the log message:

Unhandled exception IllegalArgumentException: 'Illegal character in path at index 9: [replace with URL]' during execution of task with name 'my-task-name'. Treating as failure.

Fixes

No existing issue, I suspect. Please consider this PR the issue, with a suggested fix, all bundled nicely together :)

Reminders

• Added/ran automated tests (existing tests have been run)
• Update README and/or examples (no update necessary, I think)
• Ran mvn spotless:apply

---

cc @kagkarlsson

[kagkarlsson]

Lets ship it! 🏅

[kagkarlsson]

🎉 This issue has been resolved in v14.0.1 (Release Notes)