Starknet v0.13.4 expects the 0x2 contract to be deployed

[rianhughes]

Starknet 0.13.4 includes a new system contract at address 0x2. This was deployed on integration at block 63881. Note that this contract has neither a class hash or nonce, and so must be handled differently from the normal flow where we expect these fields. We must update the contract storage at this particular address, at this particular block (different for each network), without updating the nonce or class db keys, and ensure the state commitment is handled correctly.

First 0.13.4 block on integration is 63881
https://integration-sepolia.starknet.io/feeder_gateway/get_block?blockNumber=63881
https://integration-sepolia.starknet.io/feeder_gateway/get_state_update?blockNumber=63881