SC: Support call trace deserialization in ABI serializer

[linh2931]

Add support of call trace deserialization into ABI serializer. In particular, add support for deserializing binary fields data and return_value in call_trace.

A deserialized call trace looks like

{
  "call_trace": {
    "call_ordinal": 1,
    "sender_ordinal": 0,
    "receiver": "test",
    "read_only": false,
    "hex_data": "0000000000000019ab1ca3411266697273745f706172616d5f737472696e67",
    "data": {
      "header": {
        "version": 0,
        "func_name": "4729655554853568512"
      },
      "param": "first_param_string"
    },
    "elapsed": 3,
    "console": "console line",
    "console_markers": [
      0
    ],
    "except": null,
    "error_code": null,
    "error_id": null,
    "return_value_hex_data": "64000000",
    "return_value_data": 100
  }
}

Resolves #1220

Depends on CDT AntelopeIO/cdt#353

[heifner]

My guess was that this diff was because of the difference in abi_def. That is indeed the case.
...1736800000000000000
...173680000000000
The difference results in different actions and therefore different action digest and therefore different transaction digest and therefore different block digest.

I verified a block log created by nodeos 1.x with a setabi can be read by nodeos 2.x and also a block log created via nodeos 2.x can be read by a nodeos 1.x.

Therefore, I believe these deep-mind updates are valid.

[linh2931]

Thanks for verifying this!

[spoonincode]

data_header is not guaranteed to exist-- I think this should go within the try block so if the sync call does not have a data_header then you still output the hex_data instead of throwing the exception out. Also do you want to check version in data_header?

[linh2931]

Good point! Will it.

[linh2931]

3815754