Rpc 0.8.0 errors

[FabijanC]

Usage related changes

• Address partially JSON-RPC API 0.8.0 adaptation #613
• Revert error in tx simulation and fee estimation requests is still just a stringified stack trace due to a shortcoming in blockifier, as described in this Slack thread.
• Close Execution error on estimation and simulation should return TRANSACTION_EXECUTION_ERROR #620

Development related changes

• Copy stack_trace.rs from blockifier. Can be replaced with importing once included in an official blockifier release.
• Introduce utility function for extracting RPC errors unmatched by starknet-rs (due to starknet-rs being adapted to an older RPC spec)
• Vm frame not included in the returned errors as it doesn't have recursive properties (not suitable for error-composing). Only relying on EntryPointFrame and StringFrame.
• Regarding the revert error in tx simulation and estimation still being a string, we could construct a stack trace based on that string, but it would be based on the structure of the stringified error.
• Improve testing of json rpc error structure (introduce new utility method).

Checklist:

• Checked out the contribution guidelines
• Applied formatting - ./scripts/format.sh
• No linter errors - ./scripts/clippy_check.sh
• No unused dependencies - ./scripts/check_unused_deps.sh
• No spelling errors - ./scripts/check_spelling.sh
• Performed code self-review
• Rebased to the latest commit of the target branch (or merged it into my branch)
  • Once you make the PR reviewable, please avoid force-pushing
• Updated the docs if needed - ./website/README.md
• Linked the issues resolvable by this PR - linking info
• Updated the tests if needed; all passing - execution info

[FabijanC]

As per the specification of starknet_simulateTransactions, we shouldn't return the error right away, but include the error details in the trace of the result. Shall be taken care of in #628.