Consider saving complete StateChanges to disk

[Longarithm]

This is some annoying issue we had for a long time. We don't save complete StateChanges on disk, instead we filter certain trie key types because of #2563:

match &change_with_trie_key.trie_key {
                TrieKey::Account { .. }
                | TrieKey::ContractCode { .. }
                | TrieKey::AccessKey { .. }
                | TrieKey::ContractData { .. } => {}
                _ => continue,
            };

But it makes more sense to filter by NON_DELAYED_RECEIPT_COLUMNS instead. I don't think that extra columns would occupy too much disk space. We could even consider adding delayed receipt columns for completeness.

Current logic complicates our code in certain cases. What is more, other people make reasonable assumptions that StateChanges are complete and then their experiments with storage crash because some trie node is missing.

[Longarithm]

Relevant workaround #8628