config: make Tx dedupe cache maxSize configurable

[iansuvak]

Summary

Allow node runners to set custom max size for the incoming transaction deduplication. Setting it higher could decrease the CPU load and the amount of egress data on the networking size at the cost of extra memory.

This PR introduces a new config TxIncomingFilterMaxSize set to 500k. This is just under a 10x increase from the previous value which depended on the TxBacklogSize the default for which is 26000 * 2. At periods of high transaction volume it's possible to see many more transactions than the two block estimate and this change allows individual operators to set appropriate limits based on the traffic they observe and the memory overhead that they have.

Test Plan

Existing tests

[algorandskiy]

LGTM.
Max memory estimate is 2 x 500,000 x 32 b = 32 Mb?

also need to add/generate config-v28.json (by running make generate I guess)

[iansuvak]

also need to add/generate config-v28.json (by running make generate I guess)

Thanks for the catch. I generated it locally to ensure that config tests pass locally but forgot to add the new file to my commit. Fixed now

[algorandskiy]

Please rebase - I think the e2e test failure is fixed in master

[codecov]

Codecov Report

Merging #5419 (41706dc) into master (e249905) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #5419      +/-   ##
==========================================
+ Coverage   55.39%   55.40%   +0.01%     
==========================================
  Files         447      447              
  Lines       63313    63312       -1     
==========================================
+ Hits        35072    35080       +8     
+ Misses      25849    25842       -7     
+ Partials     2392     2390       -2     

Impacted Files	Coverage Δ
config/localTemplate.go	60.60% <ø> (ø)
data/txHandler.go	73.13% <100.00%> (-0.08%)	⬇️

... and 5 files with indirect coverage changes

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

[AlgoAxel]

Your PR describes what change is being made, but could you also include why? it would be helpful if we ever need to refer back to this change. This comment describes a reasonable estimation, so why 10x it?
(I know we've discussed it plenty in team settings, but I want to make sure it's recorded)