fix(code): Use more reasonable history_gossip and history_length config params for GossipSub

[romac]

The GossipSub parameters override introduced in #236 lead to very high memory usage. This PR reverts them to their default values.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.49%. Comparing base (642c982) to head (47a83aa).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #258      +/-   ##
==========================================
+ Coverage   80.90%   81.49%   +0.60%     
==========================================
  Files          75       75              
  Lines        5606     5581      -25     
==========================================
+ Hits         4535     4548      +13     
+ Misses       1071     1033      -38     

Flag	Coverage Δ
integration	81.54% <100.00%> (+0.60%)	⬆️
mbt	8.29% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[romac]

Ran some experiments locally with 10 nodes:

History size	Heartbeat interval	Graph	Peak memory usage
50/500	1s		1.35 GB
3/5	1s		105MB
2/3	2s		88MB

Been playing with a higher heartbeat interval after reading https://ethresear.ch/t/number-duplicate-messages-in-ethereums-gossipsub-network/19921

[romac]

I have been running this branch in a 1h simulation locally with 10 nodes, and cannot see any obvious leaks.

[greg-szabo]

Merging this into the MovedToStep change so I can test them together.