Algod: Use future consensus version to test with no low resources

[jasonpaulos]

Summary

#5328 changed the initial txn counter from 0 to 1000, and simulate tests relied on this starting at 0 to predict app and asset IDs. Since we were testing with the current consensus version, not future, we didn't see any problems.

Since it's best to fix tests at development time instead of release time, I changed the relevant testing infrastructure to use consensus future instead of current. I've also fixed the simulate tests to work with a higher initial txn counter.

Note: this PR is not exhaustive. There seem to be quite a lot of tests which use the current consensus version, so it's possible more issues like this are present.

Test Plan

Tests modified.

[jasonpaulos]

This code is the same as bookkeeping.MakeGenesisBlock, so instead of adding to the duplication to account for changing the initial txn counter, I make it call that function directly

[codecov]

Codecov Report

Merging #5362 (90e45cb) into master (9e980d3) will increase coverage by 0.03%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##           master    #5362      +/-   ##
==========================================
+ Coverage   55.28%   55.31%   +0.03%     
==========================================
  Files         454      454              
  Lines       63772    63754      -18     
==========================================
+ Hits        35254    35267      +13     
+ Misses      26115    26083      -32     
- Partials     2403     2404       +1     

Impacted Files	Coverage Δ
ledger/testing/initState.go	18.60% <0.00%> (+5.48%)	⬆️
daemon/algod/api/server/v2/test/helpers.go	74.74% <100.00%> (ø)

... and 16 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[ahangsu]

lgtm, the initState.go file change seems to be directly adapting MakeGenesisBlock.