[Fraud Proof]: osp runtime issues

[Sha3nS]

Describe the bug
verifyOneStepProof run time issues occurred in local test

• verifyOneStepProof nil pointer
  To Reproduce
  rde make up occasionally occurred(maybe depend on different transaction types)

  Expected behavior
  call verifyOneStepProof normally

  Screenshots
  

• bisection execute index out of range
  To Reproduce
  rde make up occasionally occurred(maybe depend on different transaction types)

  Expected behavior
  call verifyOneStepProof normally

  Screenshots
  

• bisection execute index out of range
  The reason is bisection challenge assertion start inbox size is equal to parent assertion start inbox, it cause insufficient ExecutionStates generate by sequencer / validator, it's an error by challenge assertion create error

Additional context
No

[Kukoomomo]

• verifyOneStepProof nil pointer
  The reason for this problem is the lack of signature data in the L1toL2 transaction structure

[Kukoomomo]

• generateProofForOpcode nil point for opcode CALL 241

To Reproduce

deploy contract A and use contract B to call A then get the tx hash to generate proof for opcode 241

Expected behavior

call generateProofForOpcode normally

Screenshots

• subVerifeir call exception

To Reproduce

deploy contract A and use contract B to call A then get the tx hash to generate proof for opcode 82 and then use verifier entry to call verifier2 VerifierTypeMemoryOp and then get CALL_EXCEPTION

Expected behavior

call verifyProof normally

Screenshots

• subVerifeir call exception

To Reproduce

deploy contract A and use contract B to call A then get the tx hash to generate proof for opcode 84 and then use verifier entry to call verifier3 VerifierTypeStorageOp and then get CALL_EXCEPTION

Expected behavior

call verifyProof normally

Screenshots