vm: New CallTracer impl and capture more cases in EVM

Proposed changes

Follow-up geth changes on callTracer
- Bring in geth native.CallTracer to kaia vm.CallTracer (https://github.com/ethereum/go-ethereum/commit/fc3e6d0162a0689228bf396e9903da79bb630cb2)
- didn't create under node/cn/tracers/native to avoid import cycle.
- CallTracer's internal structure uses native types and encoded at GetResult (https://github.com/ethereum/go-ethereum/commit/fc3e6d0162a0689228bf396e9903da79bb630cb2)
- The internal structure CallFrame is converted to JSON in GetResult (for RPC)
- Result contains revertReason field (https://github.com/ethereum/go-ethereum/commit/ff1f49245d641a7268ade38cf512bdc7b26f9b7c)
- Top call frame's gasUsed field includes intrinsic gas (https://github.com/ethereum/go-ethereum/commit/0f4942214d76385c52c7917212331c9bad8b3566)
- Top call frame's gas field includes intrinsic gas (https://github.com/ethereum/go-ethereum/commit/0b76eb3708626fbd2eb9c1b58d7b4eac6a5eec15)
- Tracer captures more validation errors like "contract address collision" (See core/vm/evm.go in https://github.com/ethereum/go-ethereum/commit/064f37d6f67a012eea0bf8d410346fb1684004b4)
Follow-up geth changes on prestateTracer
- Account for simple value transfer and EXTCODEHASH (See prestate_tracer.js in https://github.com/ethereum/go-ethereum/commit/cac09a3823bcdee69c9cee7eebb70332ceefc95e)
Kaia TxType treatment
- For AccountUpdate, Cancel, and Anchoring tx types, state_transition.go calls the CaptureStart and CaptureEnd as if they are simple value transfer with value == 0 and from == to.
Add JSON testdata and makeTest scripts
- The tests are created against the node with #16 applied, and then manually inspected.

Types of changes

Please put an x in the boxes related to your change.

[x] Bugfix
[ ] New feature or enhancement
[ ] Others

Checklist

[ ] [ ] I have read the CONTRIBUTING GUIDELINES doc
[ ] I have read the CLA and signed by comment I have read the CLA Document and I hereby sign the CLA in first time contribute
[ ] Lint and unit tests pass locally with my changes ($ make test)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Related issues

Please leave the issue numbers or links related to this PR here.

Further comments

Notable changes of callTrace

Minor changes
- The output field is omitted if empty.
- The value field is sometimes omitted if it equals zero, but sometimes "0x0" is shown.
- The time field is deleted.
Top call frame's gas and gasUsed values agree with transaction and receipts.
- Affects: pretty much all transactions
- Example: Testnet 0xf3b71a6f97667dba14aef6d512c9bb01c7af43756e464c57e12b2fdfa7a9d3f2
- tx.gasLimit = 52500 (0xcd14), receipt.gasUsed = 21000 (0x5208). Note: gasLimit - intrinsicGas = 31500 (0x7b0c)

 {
   from: "0x7f0546832758f61410e81a94d7a07d55b1dfd278",
-  gas: "0x7b0c",
+  gas: "0xcd14",
   gasUsed: "0x5208",
   input: "0x",
-  output: "0x",
   to: "0xba736c844fd44c380ce19423f9f1ddcb9cd19b6c",
   type: "CALL",
   value: "0x0"
 }

Revert messages are additionally provided as geth-style revertReason field.
- Affects: Transactions reverted with a message.
- Example: Testnet 0x49aa6074a3b4970399ef2af12b109c4cb4a65ab8a833d1540e4cefa657a3c0c7
- Note that existing infrastructures relying on reverted.message field don't need change.

 {
   error: "execution reverted",
   from: "0x7f0546832758f61410e81a94d7a07d55b1dfd278",
-  gas: "0x6fb8",
+  gas: "0xc350",
   gasUsed: "0x6992",
   input: "0x96670644",
   output: "0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000962616420696e7075740000000000000000000000000000000000000000000000",
+  revertReason: "bad input",
   reverted: {
     contract: "0xe6c5b1cbf283d9482088136b8cee53fdb6c088eb",
     message: "bad input"
   },
   to: "0xe6c5b1cbf283d9482088136b8cee53fdb6c088eb",
   type: "CALL",
   value: "0x0"
 }

The DELEGATECALL trace inherits the caller's value, to match with EVM semantic.
- Affects: Transactions that execute DELEGATECALL opcode
- Example: Testnet 0x931c5af31bfb906fc20effa0f90f1a8e66edefac9879729fedd18a65d64a11be
```
{
calls: [{
from: "0xd94ed12cf3c2eded33adc58a7a09f0b4e0721cd0",
gas: "0x9b",
gasUsed: "0x62",
input: "0xc605f76c",
```
output: "0x", to: "0x3d0c6d64907b2ef39e73aa8b08ad8da9b03b9140",
type: "DELEGATECALL"
type: "DELEGATECALL",
value: "0xaa87bee538000" }],
Precompile invocations are now shown
- Affects: Transactions that execute precompiled contracts
- Example: Testnet 0xb71df5a6628cd2c193c5155c4dabbd45604a6207334c793b512293e165a04526
```
{
```
calls: [{
from: "0x813c4bd8a12e427f08e9982c958e0a6d4e05c56f",
gas: "0x18c",
gasUsed: "0x48",
input: "0x998877665544332211",
output: "0x1c32777581417de40ff9f685335ce161c493e2528c39742c5327198b95b07320",
to: "0x0000000000000000000000000000000000000002",
type: "STATICCALL"
}], from: "0x7f0546832758f61410e81a94d7a07d55b1dfd278",
gas: "0x6ad",
gas: "0x7fc5", gasUsed: "0x7fc5", input: "0x9fb83711000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000099988776655443322110000000000000000000000000000000000000000000000",
output: "0x", to: "0x813c4bd8a12e427f08e9982c958e0a6d4e05c56f", type: "CALL", value: "0x0" }
Early validation errors (e.g. max call depth exceeded, contract address collision) are now shown
- Affects: Transactions that failed with certain error codes
- Example: Testnet 0xdf06945964fb2f966c89716bb936da523964c73ee30c0f556baaad90263facfd
```
{
calls: [{
```
error: "internal failure",
error: "contract address collision", from: "0xafe64e2883b6fe56fbdddeef1536e034f2fe6c11",
gas: "0x2c2618", gasUsed: "0x2c2618", input: "0x608060405234801561000f575f80fd5b506040516101523803806101528339818101604052810190610031919061007d565b60648161003e91906100d5565b905050610108565b5f80fd5b5f819050919050565b61005c8161004a565b8114610066575f80fd5b50565b5f8151905061007781610053565b92915050565b5f6020828403121561009257610091610046565b5b5f61009f84828501610069565b91505092915050565b7f4e487b71000000000000000000000000000000000000000000000000000000005f52601160045260245ffd5b5f6100df8261004a565b91506100ea8361004a565b9250828203905081811115610102576101016100a8565b5b92915050565b603e806101145f395ff3fe60806040525f80fdfea26469706673582212201f37d242bfef7d838ebdb95c50545173bfdb701116ab06c42a6beb267ab5623864736f6c634300081a0033000000000000000000000000000000000000000000000000000000000000007b", type: "CREATE2", value: "0x0" }], }
All necessary trace fields are shown for non-EVM Tx Types (i.e. AccountUpdate, Cancel, ChainDataAnchoring)
- Affects: Such Tx Types
- Example: Testnet 0xac43859eb4064916e8be8e74645d6019cc48cb6791f68ea21d42ead6bba569b5
- These tx types are displayed as 0 value transfer to the sender itself.
```
{
```
from: "0x7f0546832758f61410e81a94d7a07d55b1dfd278",
gas: "0xcd14", gasUsed: "0xa028",
type: "",
input: "0x",
to: "0x7f0546832758f61410e81a94d7a07d55b1dfd278",
type: "CALL", value: "0x0" }

kaiachain / kaia

vm: New CallTracer impl and capture more cases in EVM #15

Proposed changes

Types of changes

Checklist

Related issues

Further comments

Notable changes of callTrace