feat: multi-crate ELF building support

[leruaa]

I renamed --binary to --binaries as it's more accurate now, but I'm not sure as it's a breaking change.

Also, maybe I can do this:

sp1/crates/build/src/utils.rs

Lines 21 to 23 in 97bb83d

	// TODO: In the future, change this to default to the package name. Will require updating
	// docs and examples.
	args.binary.clone()

[github-actions]

SP1 Performance Test Results

Branch: aurelien/gro-154-multi-crate-elf
Commit: 03fe828
Author: leruaa

program	cycles	execute (mHz)	core (kHZ)	compress (KHz)	time	success
fibonacci	11291	0.18	2.81	0.46	25s	✅
ssz-withdrawals	2757356	17.07	124.93	34.75	1m20s	✅
tendermint	12593597	6.67	264.06	99.88	2m8s	✅

[yuwen01]

Are test artifacts automatically built when running tests? Is it feasible to do this in CI now, or even with a build.rs in the test-artifacts crate?

[yuwen01]

LGTM

just for my own understanding, you use --binaries when you need to build multiple elfs for multiple sp1 programs within the same package, and you use --packages when you need to build multiple packages?

Does that mean code like this is now deprecated (from RSP)?

use sp1_build::build_program;

fn main() {
    build_program("../client-eth");
    build_program("../client-op");
    build_program("../client-linea");
}

And you'd instead do something like

build_program_with_args("path_to_workspace_root", BuildArgs{packages=vec!["client-linea", "client-op", "client-eth"], ..Default}

This is better than the previous approach, because it's parallelized.

[leruaa]

@yuwen01 Yes exactly. And if the 3 crates in your example above are the only ones in theirs workspace, you don't even neet to specify them as --packages, it will build everything. --packages is if you want to filter.