feat: SDK refactor

[mattstam]

API:

    // Local

    // Generate the proof.
    let client = ProverClient::builder()
        .local()
        .build();

    // Generate the proving key and verifying key for the given program.
    let pk = client.setup(&elf).await;

    // Generate the proof.
    let proof_result = client
        .prove(&pk, stdin)
        .compressed()
        .await;
        
    // Network

    // Generate the proof, using the specified network configuration.
    let client = ProverClient::builder()
        .network()
        .rpc_url(rpc_url)
        .private_key(private_key)
        .build();

    // Generate the proving key and verifying key for the given program.
    let pk = client.setup(Arc::from(&ELF[..])).await;

    // Generate the proof.
    let proof_result = client
        .prove(&pk, stdin)
        .compressed()
        .timeout(100)
        .cycle_limit(20_000)
        .await;

    // Old env var behavior
    
    let client = ProverClient::builder()
        .from_env();

[mattstam]

thoughts on putting this on a seperate func? I guess this was the reason we previously had a CpuProver wrapper over SP1Prover<DefaultProverComponents> so we could attach this.

[nhtyy]

Ya I think we need to expose verify somehow but lets revisit towards the end

[nhtyy]

okie looking good,

Some issues with async stuff though, lets remove ProofRequest traits, so users dont need to import it to use it, and make sure any method called run is not async.

So LocalProofRequest run just calls prove on the underlying sp1_prover, and its IntoFuture will just do a tokio::task::spawn_blocking

Now for Network its run either needs to use the blocking methods on the client if they exist or create a new runtime and block on that.

And finally for DynProofRequest its run method calls prover.prove_with_options_sync and its into future method will call prove_with_options

[nhtyy]

So I think that the DynBuilder should also expose default_{cycle_limt, timeout}?

I think that we should remove this method "create_from_env" and make the method like "build_with_env" that than overrides stuff at the end

[mattstam]

do you mean as methods? Currently I have:

/// The default timeout seconds for a proof request to be generated (4 hours).
pub const DEFAULT_TIMEOUT: u64 = 14400;

/// The default cycle limit for a proof request.
pub const DEFAULT_CYCLE_LIMIT: u64 = 100_000_000;

[nhtyy]

Yaa I think since these are common defaults we can optionally let the user set them at builder level wdyt? Otherwise default to these

[nhtyy]

Ya I think we need to expose verify somehow but lets revisit towards the end

[github-actions]

SP1 Performance Test Results

Branch: mattstam/sdk-refactor-proposal
Commit: 95e2a13
Author: mattstam

program	cycles	execute (mHz)	core (kHZ)	compress (KHz)	time	success
fibonacci	11291	0.18	2.75	0.46	25s	✅
ssz-withdrawals	2757356	16.49	126.37	34.58	1m20s	✅
tendermint	12593597	6.71	265.90	98.11	2m10s	✅

[mattstam]

note: we will update this macro to return an Arc so its easy

[mattstam]

note: I am nuking v1 and I will convert network-v2 to just network (after review because otherwise diff would be nightmarish)