fix: indexer event scanning is broken after epoch change

[mrnaveira]

Description

• In the indexer:
  • Refactored the event scanner to take into account epoch changes
  • New db methods get_oldest_scanned_epoch and delete_scanned_epochs_older_than to support the event scanning
• In the validator node:
  • Refactored the block sync task to take into account epoch changes and to use the existing up_to_epoch parameter (it was ignored previously)
  • New db method blocks_get_first_in_epoch to support the new block sync logic

Motivation and Context

Recently the epoch change logic was reworked, which broke the event scanning functionality in the indexer. This PR fixes it.

Fixes #1111

How Has This Been Tested?

Manually by running tari_swarm, doing transactions, and stopping/resuming the network

What process can a PR reviewer use to test or verify this change?

See previous section

Breaking Changes

• None
• Requires data directory to be deleted
• Other - Please specify

[github-actions]

Test Results (CI)

105 tests   - 444   104 ✅  - 445   34m 17s ⏱️ - 55m 43s
 15 suites  -  43     0 💤 ±  0 
  1 files    -   1     1 ❌ +  1 

For more details on these failures, see this check.

Results for commit 3751961. ± Comparison against base commit 7f0a322.

This pull request removes 444 tests.

Scenario: Claim and transfer confidential assets via wallet daemon: tests/features/wallet_daemon.feature:90:3
Scenario: Claim base layer burn funds with wallet daemon: tests/features/claim_burn.feature:7:3
Scenario: Confidential transfer to unexisting account: tests/features/transfer.feature:164:3
Scenario: Create account and transfer faucets via wallet daemon: tests/features/wallet_daemon.feature:8:3
Scenario: Create and mint account NFT: tests/features/wallet_daemon.feature:134:3
Scenario: Double Claim base layer burn funds with wallet daemon. should fail: tests/features/claim_burn.feature:45:3
Scenario: New validator node registers and syncs: tests/features/state_sync.feature:7:3
Scenario: Template registration and invocation in a 2-VN committee: tests/features/committee.feature:7:3
Scenario: Transfer tokens to existing account: tests/features/transfer.feature:87:3
Scenario: Transfer tokens to unexisting account: tests/features/transfer.feature:8:3
…

♻️ This comment has been updated with latest results.

[sdbondi]

LGTM small nits on the storage API

[sdbondi]

utACK