Update simulated geth client wrapper & LogPoller tests

[reductionista]

In this PR:

1. Update SimulatedBackendClient to wrap simulated.Backend & simulated.Client ( instead of deprecated backends.SimulatedBackendClient )

2. Add SetActiveClient() to SimulatedBackendClient to simulate switching from one rpc server to another while running.

3. Add RegisterHeadByNumberCallback to SimulatedBackendCilent, to register a custom callback function to be called each timeHeadByNumber() is called.

4. Add to SimulateBackendClient ability to run in "optimism mode", which behaves slightly different from geth: returns success rather than "block not found" if FilterLogs() is called with an invalid or unknown block hash.

5. Update BackupPoller test to use the previous 3 features to simulate failing over.to an out-of-sync optimism rpc server during a race condition between pulling a particular block and its corresponding logs. (This is exactly the case which motivated the creation of Backup LogPoller.) This avoids the need to use rawdb, which is no longer accessible in geth.

6. Replace markBlockAsFinalized() and markBlockAsFinalizedByHash() in LogPoller tests with finalizeThroughBlock().

7. Refactor logic in LogPoller tests previously using markBlockAsFinalized(ByHash) to make use of finalizedThroughBlock() instead.

8. Update some tests for new block timestamp behavior in Simulated Geth: automatic time increment between simulated blocks is 1ns now instead of 1s, and Client.AdjustTime() now automatically commits the current block after adjusting its timestamp

9. Update rest of tests in LogPoller and other packages to use new data types associated with (1.), instead of deprecated types

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[jmank88]

scratch file?

[reductionista]

Present status:

• All tests in LogPoller package passing

• All deprecated types have been updated (in all packages), Lint is now passing

• Seeing many errors in the Core CI tests still, but nearly all of them are one of 3 things, which seem very related and possibly have the same root cause:
  no contract code at given address
Execution reverted
  `Execution reverted: Target is not a contract"

• One weird error in a core test, that happens in CI but passes locally:
  --- FAIL: TestEVMForwarderPresenter_RenderTable (0.00s)
  forwarders_commands_test.go:48:
  Error Trace: /home/runner/work/chainlink/chainlink/core/cmd/forwarders_commands_test.go:48
  Error: "\n------------------------------------------------------\nID: \nAddress: 0x4Fc0FeeD7E3F8d9bb6758d3084aa0ff6cFB5C486\nChain ID: 4\nCreated At: 2024-05-29T04:33:50Z\n------------------------------------------------------\n" does not contain "1"

• For some reason, this error causes the Clean Go Tidy & Generate CI check to fail:
  cp: cannot create directory '../../operator_ui/..//core/web/assets': No such file or directory

I think the last one was what prompted me initially to run make generate locally, but I guess that didn't fix it.

I'm not sure how many of these errors were already in the branch I'm trying to merge into, but seems like it might be about time to merge it and rebase that branch?

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.4% Duplication on New Code

See analysis details on SonarQube