debugging: exceptions lack a stack trace

CLion debugger has an option to log a stack trace when any exception is thrown, but this is noisy, and not suitable for production.
We could try introducing a custom base exception class and using Boost.Stacktrace there, or using throw_with_trace everywhere:
https://www.boost.org/doc/libs/master/doc/html/stacktrace/getting_started.html#stacktrace.getting_started.exceptions_with_stacktrace

No source files, tests, or entry points are named. Start with the linked Boost.Stacktrace documentation and inspect how exceptions are currently handled; done means selecting and implementing a consistent approach that provides exception stack traces without relying on CLion's debugger option.

Written by the indexing model from the issue text.