blockifier_reexecution: remove fallback warn logs from SimulatedStateReader

[AvivYossef-starkware]

SimulatedStateReader is now used in the reexecution flow where
non-invoke-V3 transactions (L1 handlers, declares, deploy accounts)
are expected. Cache misses for these transaction types are normal
behavior, not warnings.

[reviewable-StarkWare]

This change is 

[AvivYossef-starkware]

• blockifier_reexecution: delete RpcStateReader methods superseded by get_block_info_with_txs #13834
• blockifier_reexecution: cache BlockInfoWithTxs in consecutive readers to dedupe RPC fetches #13833
• blockifier_reexecution: add get_block_info_with_txs for single-call block fetch #13832
• blockifier_reexecution,starknet_transaction_prover: support DeployAccount V3 in simulate prefetch #13778
• blockifier_reexecution,starknet_transaction_prover: graceful fallback on prefetch failure #13743
• blockifier_reexecution,starknet_transaction_prover: parameterize skip_fee_charge in prefetch #13738
• blockifier_reexecution: remove fallback warn logs from SimulatedStateReader #13737 👈 (View in Graphite)
• blockifier_reexecution: wire prefetch_initial_reads into replay CLI #13712
• blockifier_reexecution: add prefetch_initial_reads to ConsecutiveRpcStateReaders #13711
• blockifier_reexecution: extract contract_class_mapping_dumper into ConsecutiveRpcStateReaders #13741
• blockifier_reexecution: add PrefetchedStateReader and move from starknet_transaction_prover #13654
• main-v0.14.2

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

PR Summary

Low Risk
Low risk: this is a logging-only change that stops emitting warn! on prefetched-state cache misses while preserving the existing RPC fallback behavior.

Overview
Removes warn! logging in SimulatedStateReader when prefetched StateMaps miss on storage/nonce/class-hash/declared-contract lookups, and now silently falls back to the inner RpcStateReader for those reads.

This reduces log noise in reexecution flows where cache misses are expected (e.g., for non-invoke-v3 transaction types) without changing read behavior.

^{Reviewed by Cursor Bugbot for commit 2086d68. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Yoni-Starkware]

Why?

@Yoni-Starkware made 1 comment.
Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on noaov1).

[AvivYossef-starkware]

When I originally added this warns,
We used it only for the transaction prover, which allows only inoke v3 txs.
But now we are going to get those warnings for almost every state read in every other tx in the replay

@AvivYossef-starkware made 1 comment.
Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on noaov1).

[Yoni-Starkware]

@Yoni-Starkware reviewed 1 file and all commit messages, and made 1 comment.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on noaov1).