feat(proposer): remove manual network proof timeout

[ratankaliani]

The proof timeout logic was necessary when we could not assume that the network would correctly set the status of the proof to failed, and the application (op-succinct) had to do this itself to re-request a proof.

This inadvertently causes a backlogged cluster to become even more backlogged.

Ex.
Requested proofs on the cluster (which are capped at maxConcurrentProofRequests per proposer) have been generating for > proofTimeout seconds (e.g. 4 hours). The application "times out" the proofs in it's own state, and re-requests the proofs, putting more load on the network.

[github-actions]

Metric	Value
Batch Start	20,634,930
Batch End	20,634,935
Witness Generation (seconds)	53
Execution Duration (seconds)	40
Total Instruction Count	1,332,721,970
Oracle Verify Cycles	289,812,086
Derivation Cycles	838,330,805
Block Execution Cycles	149,221,456
Blob Verification Cycles	101,677,936
Total SP1 Gas	1,585,430,164
Number of Blocks	6
Number of Transactions	37
Ethereum Gas Used	12,714,916
Cycles per Block	222,120,328
Cycles per Transaction	36,019,512
Transactions per Block	6
Gas Used per Block	2,119,152
Gas Used per Transaction	343,646
BN Pair Cycles	0
BN Add Cycles	0
BN Mul Cycles	0
KZG Eval Cycles	0
EC Recover Cycles	322,016