docs: config update

[ratankaliani]

Overview

Resolve the issue that caused the op-succinct-proposer to send more than MAX_CONCURRENT_PROOFS to the network.

Enable configuring an alternative environment when deploying contracts or spinning up the new proposer.

Details

• Add lastUpdatedTime on the ProofRequest.
• Modify the logic for checking that a requested proof timed out during witness generation. Instead of checking against the time at which a request was created (which is incorrect), we now check against the last time that the request was updated with the lastUpdatedTime.
  • Previously, this caused the proposer to spam proofs.
  • Ex. The proposer creates many SPAN proof requests. Due to the maxConcurrentProofRequests limit, only 10 proofs are sent to witness generation. These proofs take ~1 hour to fulfill. Now, the new proofs are requested. While they're in witness generation (and their ProverRequestId is set to nil), the proposer checks if the proofs have timed out (as it doesn't have a direct way of polling that a proof is in the witness generation status).
• More informative logging.
• To supply an alternative environment (e.g. .env.conduit) when deploying the contracts or running the op-succinct-proposer, just pass the ENV_FILE argument.