fix!: time based lookback in oov3-bot

[Reinis-FRP]

Motivation

OOv3 bot looks for assertions that can be settled using block range based lookback. Sometimes this is not sufficient and we cannot guarantee that even standard 2h challenge window assertions get detected. This is particularly an issue for chains that don't have fixed block times (e.g. Arbitrum).

Summary

Use BlockFinder for time based lookback and set the default to use 72h that should cover most use cases.

Testing

Check a box to describe how you tested these changes and list the steps for reviewers to test.

• [x] Ran end-to-end test, running the code as in production
• [ ] New unit tests created
• [ ] Existing tests adequate, no new tests required
• [ ] All existing tests pass
• [ ] Untested

Since BlockFinder does not work in local test network, this was tested in production:

• Made test assertion here
• Bot picked it up 2h later (after challenge window) after 27k blocks had passed:

  2024-01-12 20:33:51 [warn]: {
  "at": "OOv3Bot",
  "message": "Assertion Settled ✅",
  "mrkdwn": "Assertion with ID 0xd7f821a847dbf4f76c10bcd3631d430328fddb6ba036f8cc41604e1079f64b33 settled in transaction <https://arbiscan.io/tx/0xbb738e58a7cdd9b8e3cdba9d5c2d6f9ce1f29849e1b811204a39fdacfcf822d7|0xbb7...f822d7>. Claim: test assertion: 1+1=2. Settlement Resolution: true. Identifier: ASSERT_TRUTH. Bond: 500.00 USDC.",
  "notificationPath": "optimistic-oracle",
  "bot-identifier": "NO_BOT_ID"
  }

Issue(s)

Fixes https://linear.app/uma/issue/UMA-2236/fix-oov3-settlement-bot-lookback

[linear[bot]]

UMA-2236 Fix OOv3 settlement bot lookback