Split storage ranges at the end of snap ranges sync to parallelize execution

[damian-orzechowski]

Changes

At the end of state ranges sync, when only large storage trie is left to be synced, snap batches will be processed sequentially. This change adds a mechanism to detect such scenario and partition the space left to sync in a similar way that account ranges are partition at the start of snap sync. Parallel execution of the batches improves last phase - usually manifesting itself as "stuck" at 100% progress.

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: Description

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.

[LukaszRozmej]

Why not just partition storage tries by default always?

[damian-orzechowski]

Why not just partition storage tries by default always?

Created a different approach here: #7733