feat(katana-rpc): add ContractErrorData when it applies

[glihm]

Add the actual data for the ContractError (40) which is the only one in the specification of have such inner error object.

When we will be compatible with 0.6.0, TransactionExecutionError will also have one.

@kariy I don't know if it's the most elegant way to do so. But introducing the object into the ContractError variant break the Copy trait.

[kariy]

I think it's more idiomatic to make the ContractError variant as a struct.

Removing the Copy trait should be fine.

[glihm]

I think it's more idiomatic to make the ContractError variant as a struct.

Removing the Copy trait should be fine.

That's a nice option, I've made a new proposition. The only point is that, we can't cast into i32 anymore if we have internal fields in the variants.
For this reason, I've proposed to move the error code (which is a bit less readable IMO for the code). But we have a better extensibility in the future I think when new error may have data fields.

I've also tried to introduce a new type ApiRpcError, that katana and starknet APIs can return. And then we only use the convertion from ApiRpcError into jsonrpsee::Error. But I'm not sure if it's a good think to add a new layer of abstraction here.

WDYT?