Add automated stress test to base node wallet

[hansieodendaal]

Description

1. This change adds the ability to perform an automated stress test that uses a command file as input. The command file accommodates one optional coin-split command and one or more make-it-rain commands. The number and amount of
   test UTXOs will be assessed, and if found to be inadequate to perform the entire test, the coin-split will be attempted if requested. In the event of a coin-split, the wallet will be monitored for up to 30 minutes to determine if a sufficient number of UTXOs became available, and when that is achieved, the stress test will start. The make-it-rain commands can be scheduled to start at a specific time, thus the test can be started in advance.
2. Updated the make-it-rain to not rely on peer discovery anymore before starting the test, but rather using a ping transaction's direct send results to determine connectivity.
3. Fixed a bug in the make-it-rain transaction rate controller where subtracting two unsigned ints resulted in a large positive number, which broke the logic.
4. Fixed clippy warnings.
5. Fixed doc test.

Example console command:

stress-test ../stress_test.txt

Example command file:

# We need these!
coin-split 10000 121
# Let us stress the network
make-it-rain 10 15 8000 1 now 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518 Testing the network!
make-it-rain 10 15 9000 1 now 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518 Testing the network!

Example terminal output - test could not be performed due to time-out:

>> stress-test ..\stress_test.txt

>>
The test requires 300 UTXOs, minimum value of 9925 each (average fee included); 
  our current wallet has 271 UTXOs that is adequate.

Command: coin-split 10000 121

coin-split 10000 99
Coin split transaction created with tx_id:
16124744115680775216
coin-split 10000 22
Coin split transaction created with tx_id:
9181473920642184746

We still need 33 UTXOs, waiting for them to be created...

We have created enough UTXOs, initiating the stress test.

Command: make-it-rain 10 15 8000 1 now 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518 Testing the network!
Command: make-it-rain 10 15 9000 1 now 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518 Testing the network!
💀 Test transaction to `7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518` timed out , cannot perform 'make-it-rain' test
💀 Test transaction to `7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518` timed out , cannot perform 'make-it-rain' test

Example terminal output - test successful:

>> stress-test ..\stress_test.txt

>>
The test requires 300 UTXOs, minimum value of 9925 each (average fee included); our current wallet has 386 UTXOs that is adequate.

Command: make-it-rain 10 15 8000 1 now 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518 Testing the network!
Command: make-it-rain 10 15 9000 1 now 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518 Testing the network!
Sending 9000 µT Tari to 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518
Sending 8000 µT Tari to 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518
Sending 8001 µT Tari to 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518
Sending 9001 µT Tari to 7ad67f1c608d25bf6126f5ce5e44cabc5f1b0464ae14efd1969d52f2dfb5c518
...

Motivation and Context

Stress tests need to be performed more frequent for testnet an easy barrier for entry for community members.

How Has This Been Tested?

Tested between three base nodes in Windows.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Feature refactor (No new feature or functional changes, but performance or technical debt improvements)
• New Tests
• Documentation

Checklist:

• I'm merging against the development branch.
• I ran cargo-fmt --all before pushing.
• I ran cargo test successfully before submitting my PR.
• I have squashed my commits into a single commit.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[delta1]

I managed to test the happy path since I had enough utxos. Haven't tested the coin-split path though.

[hansieodendaal]

I managed to test the happy path since I had enough utxos. Haven't tested the coin-split path though.

Thanks!