feat: adjust block sync timeouts

[hansieodendaal]

Description

Adjusted block sync timeouts to enable block sync over tor when we have many full blocks. Previous values were unrealistic and unfeasible. This PR provides feasible default values for full blocks sync over tor for a fresh base node.

Motivation and Context

A recent stress test on esemeralda provided a blockchain with many full blocks. Performing a fresh base node block sync over tor in a controlled environment proved impossible due to inherent network latencies. Although there may be a fix to improve the tor latencies with full blocks sync, it is not yet available.

2024-05-14 17:16:00.091735600 [c::bn::block_sync] TRACE [block sync timings] 1.1 #1501 Latency in 134.48s
2024-05-14 17:18:56.454123100 [c::bn::block_sync] TRACE [block sync timings] 1.1 #1502 Latency in 173.69s
2024-05-14 17:21:15.535060700 [c::bn::block_sync] TRACE [block sync timings] 1.1 #1503 Latency in 136.89s
2024-05-14 17:24:15.852873000 [c::bn::block_sync] TRACE [block sync timings] 1.1 #1504 Latency in 178.57s
2024-05-14 17:26:53.273228300 [c::bn::block_sync] TRACE [block sync timings] 1.1 #1505 Latency in 155.62s

How Has This Been Tested?

Many system-level tests.

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

Code review and system-level tests.

Breaking Changes

• None
• Requires data directory on base node to be deleted
• Requires hard fork
• Other - Please specify

[github-actions]

Test Results (CI)

    3 files    120 suites   43m 57s ⏱️
1 279 tests 1 279 ✅ 0 💤 0 ❌
3 829 runs  3 829 ✅ 0 💤 0 ❌

Results for commit 25d4b93.

[github-actions]

Test Results (Integration tests)

 2 files  11 suites   25m 3s ⏱️
33 tests 30 ✅ 0 💤 3 ❌
37 runs  32 ✅ 0 💤 5 ❌

For more details on these failures, see this check.

Results for commit 25d4b93.