conductor: executes_soft_first_then_updates_firm test is flaky

[ethanoroshiba]

The conductor::soft_and_firm::executes_soft_first_then_updates_firm test is flaky for me locally, with the following output:

thread 'soft_and_firm::executes_soft_first_then_updates_firm' panicked at crates/astria-conductor/tests/blackbox/soft_and_firm.rs:109:6:
Conductor should have executed the block and updated the soft commitment state within 500ms: Elapsed(())
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'tokio-runtime-worker' panicked at crates/astria-grpc-mock/src/mock_server.rs:194:17:
Verifications failed:
- Mock #2 for RPC get_filtered_sequencer_block.
        Expected range of matching incoming requests: 1 <= x
        Number of matched requests with valid mock responses: 0
        Number of matched requests with bad mock responses: 0

- Mock #3 for RPC execute_block.
        Expected range of matching incoming requests: == 1
        Number of matched requests with valid mock responses: 0
        Number of matched requests with bad mock responses: 0

- Mock #4 for RPC update_commitment_state.
        Expected range of matching incoming requests: == 1
        Number of matched requests with valid mock responses: 0
        Number of matched requests with bad mock responses: 0


Received requests:
- Request #0
        RPC name: get_commitment_state
        Requests Protobuf as JSON
        {}
- Request #1
        RPC name: get_genesis_info
        Requests Protobuf as JSON
        {}



failures:
    soft_and_firm::executes_soft_first_then_updates_firm