Fix decoder parsing with new storage tries

[Nashtare]

We are not adding a default new trie mapped to a created address, which can cause errors in parsing if trying to write to storage of a newly created account.

Fixes a bunch of missing storage trie for address FOO on the test chain (I'm not including new payloads on the test cases folder because I am still trying to debug follow-up issues with some of these blocks on the prover side, but I can share payloads, the consistent-with-header integration test passes now).

[Nashtare]

The Validate PR job is failing because it crashed parsing, as I had forgotten the closing "" in "the consistent-with-header". Changing the PR description and re-running the job doesn't work, it cached the initial version. Guess we can just ignore it for this PR.