[Feature] Display the full JSON-RPC call in the logs that failed

Currently if something goes wrong with a JSON RPC call (eth-calls, decoding, etc) there is just a message like this displayed:

failed to process trigger: block #21041413 (0x0000…b378), transaction a44fa1857fa5448419ff94682de1ffeccaa74eb0d6dc9d0de8fe37c6c2a90746: Decoding function outputs for the call Function { name: "withdraw", inputs: [], outputs: [Param { name: "", kind: Uint(256), internal_type: None }], constant: None, state_mutability: NonPayable } failed, raw output: : Invalid name: please ensure the contract and method you're calling exist! failed to decode empty bytes. if you're using jsonrpc this is likely due to jsonrpc returning 0x in case contract or method don't exist

(From this example subgraph: https://thegraph.com/hosted-service/subgraph/bsamuels453/yearn-fantom-validation?selected=logs, deployment id: QmNhTkng5LLvdCXbK6JSoeU8tSW18wo3tPpm5mMM3Sd4FY)

This alone does not provide enough information to reproduce.

What is the expected behavior?

It would be great to have the exact JSON RPC call written in the logs so we can reproduce and troubleshoot the underlying issue.

Commencez par localiser le chemin de journalisation des échecs JSON-RPC dans graph-node et reproduisez l’échec d’exemple de l’issue. Suivez l’opération eth-call ou de décodage qui a échoué afin de déterminer où les détails de sa requête sont disponibles ; le travail est considéré comme terminé lorsque l’appel JSON-RPC exact est inclus dans les logs pour les échecs comparables et reste utile pour reproduire l’erreur sous-jacente.