fix(rpc test): StateCall and StateReplay

[hanabi1224]

Summary of changes

For a detailed explanation, see #4432 (comment)

Changes introduced in this pull request:

• fix RPC test for StateCall and StateReplay by ignoring the ReturnTrace::exit_code field

Manually tested with the same snapshot that causes CI failures in https://github.com/ChainSafe/forest/actions/runs/9593268587/job/26453560366#step:5:39

forest-tool api compare /data/forest_snapshot_calibnet_2024-06-20_height_1718049.forest.car.zst --forest *** --lotus *** --n-tipsets 10 --filter-file /data/filter-list --miner-address t0111551 --worker-address t3sw466j35hqjbch5x7tcr7ona6idsgzypoturfci2ajqsfrrwhp7ty3ythtd7x646adaidnvxpdr5b2ftcciq

     Running `target/quick/forest-tool api compare /home/me/fr/snapshots/calibnet/forest_snapshot_calibnet_2024-06-20_height_1718049.forest.car.zst --filter StateReplay`
| RPC Method                | Forest | Lotus |
|---------------------------|--------|-------|
| Filecoin.StateReplay (48) | Valid  | Valid |

     Running `target/quick/forest-tool api compare /home/me/fr/snapshots/calibnet/forest_snapshot_calibnet_2024-06-20_height_1718049.forest.car.zst --filter StateCall`
| RPC Method              | Forest | Lotus |
|-------------------------|--------|-------|
| Filecoin.StateCall (48) | Valid  | Valid |

Reference issue to close (if applicable)

Closes

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

[LesnyRumcajs]

I recommend we don't merge this so that it's clearly visible that the Forest and Lotus output differs at the currently used versions.

[LesnyRumcajs]

@hanabi1224 what do we do with this draft?