[Misc]: Improve error handling by adding contexts

[satoshiotomakan]

Description

Currently, it's complicated to debug errors WalletCore returns, especially if the error is related to incorrect SigningInput parameters, as the error codes are too abstract, eg SigningError::Error_invalid_params, SigningError::Error_invalid_address and other.

In this PR, we introduce error contexts - an extension of the error messages that will help to find out which request parameter leads to the error.

Example:

A provided address (e.g. destination address) is invalid
Context:
0. Neither the private key nor the sender address is specified.

How to test

Run Rust, C++ tests

Types of changes

Checklist

• Create pull request as draft initially, unless its complete.
• Add tests to cover changes as needed.
• Update documentation as needed.
• If there is a related Issue, mention it in the description.

If you're adding a new blockchain

• I have read the guidelines for adding a new blockchain.

[lamafab]

I checked tw_coin_entry::error and it looks good imo. The intended usage of this seems to be for debugging purposes via the Display trait (ie. format_context), I assume?

[satoshiotomakan]

Hi @lamafab, exactly.
I think some of the conversions seem complicated. For example, From<KeyPairError> is implemented for TWError<SigningErrorType>, not for SigningErrorType as it suppose to be because the errors are declared in different crates (not in tw_coin_entry).
So we could actually implement From<KeyPairError> for SigningErrorType in tw_proto, but then tw_proto should depend on tw_key_pair

[github-actions]

Binary size comparison

➡️ aarch64-apple-ios:

- 11.50 MB
+ 11.72 MB 	 +232 KB

➡️ aarch64-apple-ios-sim:

- 11.50 MB
+ 11.72 MB 	 +232 KB

➡️ aarch64-linux-android:

- 14.84 MB
+ 15.22 MB 	 +383 KB

➡️ armv7-linux-androideabi:

- 12.48 MB
+ 12.71 MB 	 +239 KB

➡️ wasm32-unknown-emscripten:

- 10.25 MB
+ 10.55 MB 	 +307 KB