fix(consensus)!: remove substate value when substate is DOWN

[sdbondi]

Description

fix(consensus)!: remove substate value when substate is DOWN
fix(consensus): remove lock conflict entries when transactions are/will be aborted
fix(event scanner)!: don't request unused substate and transaction data when syncing events
fix(consensus): simplify pledging and fix a couple of bugs

Motivation and Context

Greatly reduces the storage required by removing historical state.

How Has This Been Tested?

Manually, tariswap test

Breaking Changes

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

[github-actions]

Test Results (CI)

594 tests   - 24   594 ✅  - 24   1h 26m 22s ⏱️ - 3h 27m 44s
 55 suites  - 13     0 💤 ± 0 
  1 files    -  1     0 ❌ ± 0 

Results for commit f7af3af. ± Comparison against base commit ec0eb2e.

This pull request removes 24 tests.

Scenario: Claim and transfer confidential assets via wallet daemon: tests/features/wallet_daemon.feature:83:3
Scenario: Claim base layer burn funds with wallet daemon: tests/features/claim_burn.feature:9:3
Scenario: Claim validator fees: tests/features/claim_fees.feature:10:3
Scenario: Concurrent calls to the Counter template: tests/features/concurrency.feature:7:3
Scenario: Confidential transfer to account that does not previously exist: tests/features/transfer.feature:151:3
Scenario: Counter template registration and invocation multiple times: tests/features/counter.feature:46:3
Scenario: Counter template registration and invocation once: tests/features/counter.feature:8: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:125:3
Scenario: Create resource and mint in one transaction: tests/features/nft.feature:80:3
…

♻️ This comment has been updated with latest results.