cli: adjust upload-state command to upload key-value pairs instead of full MPT traversal

[AliceInHunterland]

Ref. #3782

[codecov]

Codecov Report

Attention: Patch coverage is 39.13043% with 14 lines in your changes missing coverage. Please review.

Project coverage is 82.56%. Comparing base (42beabc) to head (f60feef).
Report is 3 commits behind head on master.

Files with missing lines	Patch %	Lines
cli/util/upload_state.go	0.00%	12 Missing ⚠️
cli/server/server.go	77.77%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3845      +/-   ##
==========================================
+ Coverage   82.53%   82.56%   +0.02%     
==========================================
  Files         342      342              
  Lines       47891    47887       -4     
==========================================
+ Hits        39527    39537      +10     
+ Misses       6730     6708      -22     
- Partials     1634     1642       +8     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[roman-khimov]

So, where is the real description of the problem?

[roman-khimov]

Size/speed difference with the old one?

[AliceInHunterland]

Current:

INFO	uploaded state object	{"object ID": "EGDc7u1iwJkqa43fqkUqtNh616KhPNXR8rVPeMXf33EX", "height": 7000000, "time spent": "35m53.933537042s"}
Size: 115554714

INFO	uploaded state object	{"object ID": "6BkdkLURYdTCaxiCrQxLwCxLAJkXVu4JycbNAvGTJKqp", "height": 7000000, "time spent": "26m11.683275625s"}

INFO	uploaded state object	{"object ID": "8aXv7ksvUomzotURmbgD7cFciKzMKF8jnKy32LqEQpVS", "height": 7000000, "time spent": "1h25m15.404159667s"}

previous (full mpt):

INFO	uploaded state object	{"object ID": "Hf4pUdEXRMYSpuA4is58guTkTmuV5B6HAczsQzbw85R3", "height": 7000000, "time spent": "28m3.138069208s"}
Size: 193742996

INFO	uploaded state object	{"object ID": "5ThvHYpPG7Zo3hFbjxGxDHJ678oJqZSXKEqKzMQdDtYA", "height": 7000000, "time spent": "26m17.047394583s"}

[AnnaShaleva]

Otherwise LGTM.

[AnnaShaleva]

"time spent": "1h25m15.404159667s"

This is unexpectedly slow and differs from previous two results. At the same time I'm not sure if we can optimize full MPT traversal process because we anyway need to traverse the whole tree unwrapping all hash nodes on the way.

Another point I'd like to mention here is that we still have #3103. This issue does not directly affect the upload-state, we still have all storage items included in the resulting dump file. But we need to keep in mind that the order of these storage items is different from the one we might get via standard DB-based seek implementation.