feat: cargo ceno

[lightsing]

to try, in ceno/ceno_cli/example dir, run:

$ cargo install --path .. --locked
$ cargo ceno run --release --hints 10 --public-io 4 --out-proof proof.bin --out-vk vk.bin

• cargo ceno build
• cargo ceno run
• cargo ceno keygen
• cargo ceno prove
• cargo ceno verify

resolve #876

close #813
close #814
close #818
close #819

[lispc]

some comments for the e2e.rs

1. let us still allow load an elf from args. instead of a static predefined program. Though it sounds better to use a fixed elf for a test, but now many people are still use it for day to day tests/benches, let us keep its behavior for a while.
2. soundness_test, it is part of the bin/e2e.rs, it is part of test. Not part of cargo ceno cli. So in cargo ceno verify, we should not run it. This function should not be located inside a common library-level src file, should be located in bin/example/tests place. Should not move? Or move it out of verify. Make it same level with verify. So in e2e.rs, codes will be like prove(); verify(); soundness_test(); (we move verify into src/e2e.rs, but keep soundness_test in bin/e2e.rs)

[hero78119]

👍