feat: add logs for incoming API requests

[MexicanAce]

What 💻

• Add logs for incoming API requests
• Update not_implemented logs to warnings
• Update version number to match latest release
• Fix unit test

Why ✋

• This shows a clearer picture of what's happening against the node. When debugging an interaction with other tools like MetaMask, Portal, Block Explorer, etc. it's VERY useful to know what requests have been made and might be silently failing
• Warning better encapsulated the response now that it's contrasted against the initial request
• This was out of date per the latest release
• Overlooked prior to merge of a refactor when implementing eth_feeHistory

Evidence 📷

Example of new not_implemented logs:

Output of make test-e2e with default logs:

Output of eth_getBlockByNumber with trace log level:

Notes 📝

• I chose to reference the LevelFilter in the middleware because I wanted to avoid duplicate log statements for trace and info. The info is meant to be truncated/short/concise, while trace log can be MASSIVE depending on the incoming payload.

[dutterbutter]

Not sure I like this with the info level tbh. Could get quite noisy with more complicated deployments. Perhaps this is better suited for a trace level that can be introduced?

[dutterbutter]

@MexicanAce please address conflicts

[MexicanAce]

Not sure I like this with the info level tbh. Could get quite noisy with more complicated deployments. Perhaps this is better suited for a trace level that can be introduced?

Discussed offline and added the LogLevel::Trace support with the responses and full requests now being logged accordingly (See updated screenshot in PR description). The truncated requests will be left for now, and we'll wait to hear from users if it's too noisy/not flexible enough for their needs.

Ultimately, we want to discover the most useful default console output for era_test_node run.