Str-700: Preparation work for the prover CI performance metrics

[evgenyzdanovich]

Description

Preparation work for the prover CI performance metrics. Includes:

• define ProofReport simple structure
• factor out bin/prover-client/zkvm into a separate crate. Reuse this crate in provers/tests and de-duplicate some code. Later use it for in prover CI performance metrics.
• Adjust Cargo.lock files in provers/

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature/Enhancement (non-breaking change which adds functionality or enhances an existing one)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor
• New or updated tests
• Dependency Update

Notes to Reviewers

Checklist

• I have performed a self-review of my code.
• I have commented my code where necessary.
• I have updated the documentation if needed.
• My changes do not introduce new warnings.
• I have added tests that prove my changes are effective or that my feature works.
• New and existing tests pass with my changes.

Related Issues

Unblocks STR-651.

[codecov]

Codecov Report

Attention: Patch coverage is 64.00000% with 27 lines in your changes missing coverage. Please review.

Project coverage is 56.72%. Comparing base (5a42f42) to head (e978582).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
crates/zkvm/zkvm/src/prover.rs	0.00%	9 Missing ⚠️
crates/zkvm/adapters/native/src/host.rs	0.00%	7 Missing ⚠️
crates/zkvm/adapters/sp1/src/host.rs	0.00%	7 Missing ⚠️
crates/zkvm/hosts/src/lib.rs	50.00%	3 Missing ⚠️
bin/prover-client/src/primitives/vms.rs	0.00%	1 Missing ⚠️

@@            Coverage Diff             @@
##             main     #546      +/-   ##
==========================================
- Coverage   56.73%   56.72%   -0.02%     
==========================================
  Files         308      309       +1     
  Lines       31316    31387      +71     
==========================================
+ Hits        17768    17805      +37     
- Misses      13548    13582      +34     

Files with missing lines	Coverage Δ
bin/prover-client/src/main.rs	0.00% <ø> (ø)
bin/prover-client/src/primitives/prover_input.rs	0.00% <ø> (ø)
bin/prover-client/src/prover.rs	0.00% <ø> (ø)
crates/zkvm/hosts/src/native.rs	100.00% <100.00%> (ø)
crates/zkvm/hosts/src/sp1.rs	0.00% <ø> (ø)
crates/zkvm/zkvm/src/host.rs	100.00% <ø> (ø)
crates/zkvm/zkvm/src/proof.rs	46.80% <ø> (ø)
bin/prover-client/src/primitives/vms.rs	0.00% <0.00%> (ø)
crates/zkvm/hosts/src/lib.rs	50.00% <50.00%> (ø)
crates/zkvm/adapters/native/src/host.rs	58.82% <0.00%> (-15.26%)	⬇️
... and 2 more

... and 1 file with indirect coverage changes

[storopoli]

Cosmetic nits.
Otherwise looks good and will ACK it.
Nice work

[delbonis]

Correct me if my understanding of how this works is incorrect but I would think that the proof generators should have the input be based on the block ranges so that it uniquely refers to what we're making the proof about. So that if we run the proof gen with the same input twice we always get the same proof.

Otherwise, concur with Jose's comments but looks well-reasoned.

[evgenyzdanovich]

@delbonis Yes, you are correct. Isn't it the case for the current prover generators in the tests? I don't quite get your concerns, would appreciate if you unwrap your thinking more.

Generators are used in tests and operate on the test data (test btc block segment, ee block segment, etc). The inputs are defined directly in test cases. Generators input currently work as a convertor into the underlying prover input (for the underlying prover).

[delbonis]

Yeah I'm seeing it in the other PR now. Not an issue that can be solved here.

[storopoli]

ACK 55ac98c

[storopoli]

ACK 0aa4b56

[storopoli]

ACK e978582