fix: Eth Event Receipt Logs: use event index for logs

[aarshkshah1992]

Closes #12254.

[rvagg]

As per my testing methodology for mainnet in #12262 (comment) (using a recent transaction for that same contract):

time curl http://localhost:1234/rpc/v1 -X POST -H "Content-Type: application/json" --data '{"method":"eth_getTransactionReceipt","params":["0x5822ec9187b621b6bdcdbea41c7b52aa2d1d1c88dd9decb38a8f5c6004b14603"],"id":1,"jsonrpc":"2.0"}' | jq .result.logs > /tmp/transaction_receipt.logs
real    0m0.017s

time curl http://localhost:1234/rpc/v1 -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getLogs","params":[{"fromBlock": "0x3eb89b", "toBlock": "0x3eb89b"}],"id":1}' | jq '[.result[] | select(.transactionHash == "0x5822ec9187b621b6bdcdbea41c7b52aa2d1d1c88dd9decb38a8f5c6004b14603")]' > /tmp/get_logs.logs
real    0m0.011s

diff /tmp/transaction_receipt.logs /tmp/get_logs.logs

(no output)

So it looks correct. In this case logIndex starts at 0x77.

eth_getTransactionReceipt is taking longer here than eth_getLogs. Running them repeatedly shows a fairly consistent timing averaging around 0.017s vs 0.011s. I think that can be explained by needing to do a bunch of blockstore loads and a call to ComputeGasOutputs.

[rvagg]

@aarshkshah1992 I just discovered this: #10287 which has some notes about potential speed-ups. Not necessary for this PR but important to file away in the memory banks because it goes to the speed concerns that are similar to trace_block and trace_filter.

[aarshkshah1992]

@rvagg Yeah I am putting together a list of high value work items for RPC and will add it there.

[rvagg]

A few suggestions in there