Seperate Proving from Execution

[austbot]

As and output of #27 , we need to separate the execution of the guest and the proving of the trace into separate stages of the pipeline.

Currently what happens is Ingester notifies the runner, which then tries to claim the execution, we will try to resolve public inputs and determine if this image is worth running and proving, if so we try to claim, then if we win the claim we try to resolve any private inputs, then we send all this to the prover to execute and prove. In this flow we execute and prove right away. Useful information, such as execution cycles, proof segments is lost and not available to the decision to claim the compute or not.

The new flow needs to separate the prover from execution.