Fix goerli state db size assumptions

[MarekM25]

Changes

Fixed tests assumptions about the size of goerli chain

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: tests fix

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

Optional. Remove if not applicable.

Documentation

Requires documentation update

• Yes
• No

If yes, link the PR to the docs update or the issue with the details labeled docs. Remove if not applicable.

Requires explanation in Release Notes

• Yes
• No

If yes, fill in the details here. Remove if not applicable.

Remarks

Optional. Remove if not applicable.

[kamilchodola]

@MarekM25
Current goerli size:

50G	./sedge-data/execution-data/nethermind_db/goerli/state/0
50G	./sedge-data/execution-data/nethermind_db/goerli/state
32G	./sedge-data/execution-data/nethermind_db/goerli/receipts
172G	./sedge-data/execution-data/nethermind_db/goerli/blocks
7.2G	./sedge-data/execution-data/nethermind_db/goerli/code
8.0K	./sedge-data/execution-data/nethermind_db/goerli/peers
4.1M	./sedge-data/execution-data/nethermind_db/goerli/witness
412M	./sedge-data/execution-data/nethermind_db/goerli/blockInfos
2.4G	./sedge-data/execution-data/nethermind_db/goerli/bloom
3.5G	./sedge-data/execution-data/nethermind_db/goerli/headers
4.1M	./sedge-data/execution-data/nethermind_db/goerli/canonicalHashTrie
4.2M	./sedge-data/execution-data/nethermind_db/goerli/metadata
1.4M	./sedge-data/execution-data/nethermind_db/goerli/discoveryNodes
267G	./sedge-data/execution-data/nethermind_db/goerli
267G	./sedge-data/execution-data/nethermind_db

To what this value You changed is referring to?

[MarekM25]

Thx for these stats - super useful. I think it is better to update those tests as we would reach 58 GB quickly and it is a blocker for now for many PRs. However, I will update chain calculation soon