fix: Fix issue with incorrect recognition of initial writes

[mm-zk]

What 💻

• Fixed a bug with incorrect marking of initial writes, which resulted in larger pubdata estimation when replaying transactions

Why ✋

• Each write to storage means, that we have to charge user some pubdata, to cover the cost of writing this data down to L1. But the costs are a little bit lower, if we had written this key in the past (we charge 32 bytes for the first write of the key, and 4 bytes for subsequents writes)
• This improves the gas computation correctness - which is important when replaying the transactions that use close to their gas limit (like the one below - 0xb0f917b869172db5123e7a63bc0f9ef4fa7498f1db34d094250087578136fde6)

Evidence 📷

We are still around 100 gas off, but before this fix, the delta was over 50k

[MexicanAce]

LGTM, worst case we over estimate once.

Thought about adding a warning about this in the console, but don't know if it's really worth it