Add context to contract exceptions

[YaroShkvorets]

Problem

There is that annoying problem with errors coming from smart contracts.
When your smart contract makes inline action calls to external contracts and one of these actions fails, you just get an error with zero context, so you can’t tell which smart contract and action that error came from. You can probably recognize your own errors but not some random errors coming from other contracts.

I.e. you only get this:

Error 3070002: Runtime Error Processing WASM
Error Details:
access violation
pending console output:
Stack Trace:
executor.cpp:257 execute
apply_context.cpp:124 exec_one

Assertion "check" failures also have this problem:

Error 3050003: eosio_assert_message assertion failure
Error Details:
assertion failure with message: read
pending console output:
Stack Trace:
cf_system.cpp:22 eosio_assert_message
apply_context.cpp:124 exec_one

This makes debugging quite painful.

Proposal

Add additional context to the error message:

• smart contract account
• action name
• receiver (to distinguish action calls from notification handlers)