Improve `verify benchmark results` time (even) more by using debug (rather than release) build

### Is your feature request related to a problem or challenge?

While reviewing https://github.com/apache/arrow-datafusion/pull/7708 from @sarutak I spent time looking into what `plan_q` does and it is not at all clear to me it needs to be built in release mode:

https://github.com/apache/arrow-datafusion/blob/46cdb8c2dc495e8063a0adc5c3f9ac82b136e72e/benchmarks/src/tpch/run.rs#L297-L453

### Describe the solution you'd like

Since the benchmark verifies the plans (rather than actually running them). I think it is ok to use debug mode (rather than release) mode which compiles faster and will have more reuse with the subsequent call to `cargo test --test sqllogictests`

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Inizia in benchmarks/src/tpch/run.rs, intorno al codice plan_q indicato, e segui come viene compilato il benchmark di verifica. Confronta la compilazione del benchmark con la successiva invocazione di cargo test --test sqllogictests; il lavoro è completato quando la verifica usa la modalità debug senza modificare i controlli del piano né il comportamento del benchmark.

Scritto dal modello di indicizzazione a partire dal testo della issue.