Difficulty adjustment fix between golang and rusty nodes

[okilisan]

Adjust difficulty managment between rusty and golang nodes during the first block window
This smells like a kaspa codebase issue as they are using only rusty nodes in testnet

[lemois-1337]

1. Sync in testnet-1 works fine now including khashv1 and khashv2 blocks, no regression anymore.
2. Sync in mainnet works fine as well, it was already before due to >2641 blocks for difficulty window, no regression.

Need to check why several test re-runs fail with:

2024-09-02 17:53:42.335 [DBG] POWK: Using khashv2 2 2
2024-09-02 17:53:42.335 [DBG] BLVA: block a00573f1d892a84af10e9dbbd5308dc8eba13a4e525613748b84c99c64b0cc4b blue score is 96
2024-09-02 17:53:42.335 [DBG] MDMN: a00573f1d892a84af10e9dbbd5308dc8eba13a4e525613748b84c99c64b0cc4b merge depth root not found in store - calculating
2024-09-02 17:53:42.335 [DBG] MDMN: a00573f1d892a84af10e9dbbd5308dc8eba13a4e525613748b84c99c64b0cc4b blue score lower then merge depth - returning genesis as merge depth root
2024-09-02 17:53:42.335 [DBG] BDAG: a00573f1d892a84af10e9dbbd5308dc8eba13a4e525613748b84c99c64b0cc4b finality point not found in store - calculating
2024-09-02 17:53:42.335 [DBG] BDAG: a00573f1d892a84af10e9dbbd5308dc8eba13a4e525613748b84c99c64b0cc4b blue score lower then finality depth - returning genesis as finality point
2024-09-02 17:53:42.335 [DBG] BDAG: Skipping ValidateBodyInContext for block a00573f1d892a84af10e9dbbd5308dc8eba13a4e525613748b84c99c64b0cc4b because it's header only
2024-09-02 17:53:42.336 [DBG] BDAG: Block a00573f1d892a84af10e9dbbd5308dc8eba13a4e525613748b84c99c64b0cc4b is a header-only block so setting its status as HeaderOnly
2024-09-02 17:53:42.336 [DBG] BDAG: Block a00573f1d892a84af10e9dbbd5308dc8eba13a4e525613748b84c99c64b0cc4b validated and inserted, network hashrate: 2.00 KH/s

[lemois-1337]

@okilisan As discussed, lets update simnet and devnet and set HFDAAScore > 2641 to pass the difficulty adjustment window. In this case tests should pass.