E2E tests: catch panics from processes

[kpp]

Summary

thread 'tokio-runtime-worker' panicked at bin/citrea/tests/test_client/mod.rs:66:14:
called `Result::unwrap()` on an `Err` value: Transport(Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }))

Steps to reproduce

1. SKIP_GUEST_BUILD=1 RUST_BACKTRACE=0 make test basic_prover_test -- --nocapture

Then in stdout it actually failed to start prover:

/tmp/.tmp31cPoG/prover$ cat stdout.log 
2024-08-29T10:30:39.314520Z  INFO bitcoin_da::service: No pending transactions found
2024-08-29T10:30:39.365385Z  INFO sov_schema_db: Opened RocksDB. rocksdb_name="ledger-db"
2024-08-29T10:30:41.150422Z ERROR panic: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Elf parse error: Could not read bytes in range [0x0, 0x10)': crates/risc0-bonsai/src/host.rs:98

Expected Result

Panic to propagate from prover process up to test code