Implement chunk nodes cache for TrieRecordingStorage

[Longarithm]

When we enable challenges, fn apply will need to work with both TrieCachingStorage and TrieRecordingStorage, so we need to maintain correct nodes accounting in both of them.

IMO it's a good idea to postpone it because the current architecture around TrieStorage is not optimal, but it is also easy to forget about.

[stale]

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

[robin-near]

@Longarithm Could you elaborate on what you mean by:

the current architecture around TrieStorage is not optimal, but it is also easy to forget about.

For context, I need to implement this now to enable storage proof for stateless validation. Thanks!

[Longarithm]

The issue was that TrieRecordingStorage::get_trie_nodes_count is not implemented.

Recently I made a change which allows calling TrieRecordingStorage::storage.get_trie_nodes_count() and I think it will just work correctly.

[Longarithm]

I think #8997 (part about removing as_caching_storage, etc.) and #9004 cover what I was unhappy about.

[Longarithm]

Done in #9350 in other way.