JSONRPC request-response logging

[yaziciahmet]

Description

Added logging to each JSONRPC request and response to be able to have better debuggability of our nodes. Each request and successful response is logged with debug tracing level. Error responses are logged with warn level since it is highly likely that the error is caused by the client-side.

Original idea was to add a new tracing level for rpc request logging. But such behavior is not possible with tracing crate. Instead of that, errors are now logged to warn level, and can be searched with a filter such as level = WARN && message = rpc_error.

I initially logged the request and success responses to info level, but due to full nodes constantly spamming sequencer for new blocks through rpc, sequencer logs became full with useless rpc calls, which is not good. Another potential approach might be to make Sequencer RPC logs debug, but full node rpc logs info.

Also, prover doesn't have any rpc logs as it is unnecessary.

Linked Issues

• Fixes New tracing level for RPC Error responses #1227

Testing

I ran sequencer and full node and sent rpc requests and observed logs.

[rakanalh]

Nice!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (nightly@7c7941c). Learn more about missing BASE report.
Report is 1 commits behind head on nightly.

Additional details and impacted files

Files with missing lines	Coverage Δ
crates/common/src/rpc/mod.rs	100.0% <100.0%> (ø)
crates/ethereum-rpc/src/lib.rs	88.9% <ø> (ø)
crates/evm/src/query.rs	88.5% <ø> (ø)
crates/fullnode/src/runner.rs	85.8% <100.0%> (ø)
crates/sequencer-client/src/lib.rs	100.0% <100.0%> (ø)
crates/sequencer/src/sequencer.rs	90.3% <100.0%> (ø)

[eyusufatik]

we might want to delete enter traces to rpcs as well, I think there were some in ledger rpc, wdyt?