Replace thread-local stateful error handling with use of Results

[daira]

Currently this crate uses stateful error reporting with a thread-local variable to hold the error state (implemented by the ffi_helpers::error_handling module).

Once we have zcash/zcash#4816 (Define a "result" type for use in C++ error handling) we should replace this error handling with that.

Originally posted by @daira in #35 (comment)

[str4d]

That type will be useless here, as this FFI goes to Swift, not C++. And in any case, errors here will be handled however UniFFI handles them.

[daira]

We decide how they are reported even when using UniFFI, no? There's nothing about the Result style of reporting that is incompatible with UniFFI, I think. (But yes you're right, it won't use C++ expected.)

[pacu]

This is a very important problem to solve. The FFI throws a myriad of unstructured errors that are hard to classify and handle, that pours out to the client code and makes error handling a nightmare and represents one of the most important developer experience problems we have on the wallet team.

Swift is designed to interop with C and C++ so I don't think it would be far much more complicated than what we do now. I don't know if it would be of any help for the JNI side of things. Probably an effort that is better spent on leveraging a tool like UniFFi or similar.