feat(rpc): Log unrecognized RPC requests

[jvff]

Motivation

While preparing Zebra to support being a backend for lightwalletd, we should ensure we're not missing any RPCs sent by lightwalletd. One thing that can help is to trace the received RPCs and log errors if unrecognized RPC requests are received.

Closes #3855.

Solution

• Enable tracing of received RPC requests by default, by making the default tracing filter allow trace level output from jsonrpc-core
• Create a custom middleware for the RPC server that prints error messages if an unrecognized RPC request is received

Review

Reviewer Checklist

• Code implements Specs and Designs
• Tests for Expected Behaviour
• Tests for Errors

Follow Up Work

[codecov]

Codecov Report

Merging #3860 (5e1fd4b) into main (53e2d2e) will increase coverage by 0.05%.
The diff coverage is n/a.

❗ Current head 5e1fd4b differs from pull request most recent head 105cc94. Consider uploading reports for the commit 105cc94 to get more accurate results

@@            Coverage Diff             @@
##             main    #3860      +/-   ##
==========================================
+ Coverage   78.74%   78.80%   +0.05%     
==========================================
  Files         295      295              
  Lines       33788    33788              
==========================================
+ Hits        26606    26626      +20     
+ Misses       7182     7162      -20     

[teor2345]

I think this change could be really bad for performance, let's try to limit the performance impact?

Also, logging lots of data can cause the acceptance tests to hang.

[teor2345]

Thanks, looks great!

We can also add "Received unrecognized RPC request" to the integration test failure strings, after we get all the RPCs implemented.