caught error information lost

In a development environment, it would be useful to capture the message and perhaps the stack caught by this exception handler.

https://github.com/GoogleChromeLabs/comlink/blob/fd4b52666b1ec62784f8b45cb1108c7e40bc481d/src/comlink.ts#L377

The default message is somewhat helpful, but the error.message information gives additional context which might be helpful in resolving the upstream defect.