["Request"] better stack traces when tracing `withError`

When using `traced` with `withError` inside, the stacktrace will always point at the `withError` lambda, and won't include any information about where the error occurred originally. Adding some way to attach that extra information would be helpful so that the traces reflect the original error location