feat: increase rpc error information propagation

[penovicp]

Motivation and Resolution

The aim of this PR is to make the structured RPC error information more accessible which should enable more nuanced error handling.

Usage and development related changes

A new RpcError class is introduced which exposes the RPC error information through its properties. It also contains an isType() convenience method which can be used as follows:

try {
  ...
} catch (error) {
  if (error instanceof RpcError && error.isType('CONTRACT_NOT_FOUND')) { ... }
}

RpcError is a subclass of LibraryError that uses the same error message format as the current implementation so the changes are backward compatible.

Checklist:

• Performed a self-review of the code
• Rebased to the last commit of the target branch (or merged it into my branch)
• Linked the issues which this PR resolves
• Documented the changes in code (API docs will be generated automatically)
• Updated the tests
• All tests are passing