`trace_transaction` and `trace_replayTransaction` RPC handler panic

[DrZoltanFazekas]

Example 1: trace_transaction

cast rpc trace_transaction '["0x109167d0f8d26c84bfdf53181309d7702ed61b27e844fabb711b386bbe4ad72b"]' --rpc-url https://api.zilliqa.com --raw | jq .
Error: server returned an error response: error code -32603: Unhandled panic in RPC handler trace_transaction : Any { .. }

Example 2: trace_replayTransaction with vmTrace type of trace

cast rpc trace_replayTransaction '["0x109167d0f8d26c84bfdf53181309d7702ed61b27e844fabb711b386bbe4ad72b", ["vmTrace"]]' --rpc-url https://api.zilliqa.com --raw | jq .
Error: server returned an error response: error code -32603: Unhandled panic in RPC handler trace_replayTransaction : Any { .. }

[maxconway]

There's nowhere obvious for an unhandled panic to occur in trace_transaction or in trace_replay_transaction so this must be occuring somewhere in the transaction tracing code itself, i.e. trace_evm_transaction downwards.

TBH we should probably be reporting the actual error in these cases rather than catching it and throwing away the info