feat: do validation after adding utxos and txs

[SWvheerden]

Description

Trigger a validation task after recovery of outputs

Motivation and Context

During testing, new outputs are added slower than validation and an edge case occurs where outputs will only be validated after a new block is added again.

[github-actions]

Test Results (CI)

1 268 tests   1 268 ✅  18m 0s ⏱️
   39 suites      0 💤
    1 files        0 ❌

Results for commit d88658e.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results (Integration tests)

29 tests  +29   29 ✅ +29   11m 49s ⏱️ + 11m 49s
11 suites +11    0 💤 ± 0 
 2 files   + 2    0 ❌ ± 0 

Results for commit d88658e. ± Comparison against base commit b6b80f6.

♻️ This comment has been updated with latest results.

[hansieodendaal]

Maybe a better place to add this would be here if num_outputs_recovered>0?

            match self.get_next_peer() {
                Some(peer) => match self.attempt_sync(peer.clone()).await {
                    Ok((num_outputs_recovered, final_height, final_amount, elapsed)) => {
                        debug!(target: LOG_TARGET, "Scanned to height #{}", final_height);
                        self.finalize(num_outputs_recovered, final_height, final_amount, elapsed)?;
                        return Ok(());
                    },
                    Err(e) => {
                        warn!(
                            target: LOG_TARGET,
                            "Failed to scan UTXO's from base node {}: {}", peer, e
                        );
                        self.publish_event(UtxoScannerEvent::ScanningRoundFailed {
                            num_retries: self.num_retries,
                            retry_limit: self.retry_limit,
                            error: e.to_string(),
                        });
                        continue;
                    },
                },

I also see there are some failing unit tests.

[hansieodendaal]

utACK