fix(op-node/op-batcher): fallbackClient should ignore ethereum.NotFound error

[welkin22]

Description

fallbackClient ignores ethereum.NotFound errors when counting errors during error handling, as this error does not indicate any issues with the endpoint's health.
The fallbackClient in op-node and op-batcher was modified. Due to the multiple rpc methods in fallbackClient in op-batcher, it can be difficult to troubleshoot issues. Therefore, some new logs were added to facilitate future troubleshooting.

Rationale

We found that the fallbackClient in op-batcher always inexplicably switches endpoints, although no request error was found in the log. After investigation, it was found that the ethereum.NotFound error returned by the interface when op-batcher obtained the TransactionReceipt was counted by the fallbackClient.

Example

none

Changes

Notable changes:

• In both op-node and op-batcher, the fallbackClient ignores the ethereum.NotFound error.
• Add logs to fallbackClient in op-batcher for easier troubleshooting in the future.

[krish-nr]

/LGTM