Implement delayed chunks application for Stateless Validation

[pugachAG]

See the doc for more context.

This includes delaying applying block chunks until the next block is processed or a new chunk is needed to be produced.

[Longarithm]

It seemed to me that I can achieve all three sub-goals from Miro board for #9679 if I apply right modifications to get_apply_chunk_job_new_chunk. Unfortunately, all my attempts ended up with couple of integration-tests failing due to different reasons, including

• ChunkExtra to be stored for the block which chunk was executed
• misalignment with staking txs processing in epoch manager

So I decided to come back to previous non-async approach and iterate from it slower. Pair of fixes already helped to bring number of nayduck failures "just" to 60. I plan to reduce it further and then apply chunks asynchronously again.

[Longarithm]

Latest update: https://near.zulipchat.com/#narrow/stream/407237-pagoda.2Fcore.2Fstateless-validation/topic/delaying.20chunk.20execution/near/401389927

[Longarithm]

Quick update: we are not fully doing this anymore in scope of SV mainnet release. Main reason is that applying of old chunks is more problematic than we thought. We still want to do it, but the fix must include, together:

• replacing "apply old chunks" concept with "update validator accounts for empty chunk range"
• as new chunk in block appears, it should fix set of incoming receipts to be executed, which will be from prev chunk, included, to new chunk, excluded. Now we take "previous" range
• to be able to apply chunks eagerly, it should be possible to reapply old chunk every time when new chunk is missing, because set of receipts to execute is changing.

IIRC this is valuable as we won't have to apply receipts to make just a state sync and protocol logic becomes MUCH more consistent.